MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

AutoMobile

Earlier Revision Publisher unverified Confidence: Good (0.85)

AutoMobile is an MCP server published by jasonpearson.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does AutoMobile support the current MCP specification (2026-07-28)?

Not yet confirmed. AutoMobile is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is AutoMobile a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for AutoMobile (as of 2026-08-20).

How do I connect to AutoMobile?

AutoMobile is available via the package npm:@kaeawc/auto-mobile, the official MCP Registry under dev.jasonpearson/auto-mobile, the source repository at https://github.com/kaeawc/auto-mobile. Authentication: unknown. Transports: stdio.

Does AutoMobile support MCP revision 2025-11-25?

Yes. AutoMobile supports MCP revision 2025-11-25 (checked 2026-08-20).

Does AutoMobile support MCP revision 2026-07-28?

No. AutoMobile was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were AutoMobile's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Mobile device interaction automation via MCP

Which MCP spec revisions does AutoMobile support?

AutoMobile has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is AutoMobile?

Ranked #155 in The MCP 500 with Adoption Index 52.63 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 2,060 API ·
GitHub stars 48 API ·
GitHub forks 5 API ·
Last push 2026-09-15T10:05:40Z API ·
Repository archived no API ·

Repository and package signals for AutoMobile

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
137
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
Present
Security policy
None

Package (npm) as of

Latest version
0.0.63
Last published
First published
Releases
55
License (package)
Apache-2.0
Maintainers
1
Direct dependencies
66
Unpacked size
26.8 MB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for dev.jasonpearson/auto-mobile at version 0.0.50 - lists package npm:@kaeawc/auto-mobile and repository https://github.com/kaeawc/auto-mobile - accessed
  2. npm registry metadata for @kaeawc/auto-mobile at published version 0.0.60, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed