MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

nano-pay

Current Spec Verified Publisher unverified Confidence: Good (0.85)

nano-pay is an MCP server published by feeless402.com with verified support for the current MCP specification revision (2026-07-28). Last verified 2026-08-20.

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

Yes. nano-pay has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-20).

Is nano-pay a first-party (official) MCP server?

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

How do I connect to nano-pay?

nano-pay is available via the package pypi:feeless402, the official MCP Registry under com.feeless402/nano-pay, the source repository at https://github.com/feeless402/feeless402. Authentication: unknown. Transports: stdio.

Does nano-pay support MCP revision 2026-07-28?

Yes. nano-pay supports MCP revision 2026-07-28 (checked 2026-08-20).

When were nano-pay's facts last verified?

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

Pay for x402-priced APIs with feeless, sub-second Nano (XNO) micropayments from a local wallet.

Which MCP spec revisions does nano-pay support?

nano-pay has 1 verified spec-support record. 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 2026-07-28 Supported Source

How widely adopted is nano-pay?

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

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
GitHub stars 3 API ·
GitHub forks 0 API ·
Last push 2026-09-07T22:17:58Z API ·
Repository archived no API ·

Repository and package signals for nano-pay

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
0
Primary language
Python
License (repository)
MIT
Continuous integration
None detected
Tests
Present
Security policy
None

Declared topics: ai-agents, http-402, mcp, micropayments, nanocurrency, railhint, x402, xno — author-declared on the repository, not our taxonomy.

Package (pypi) as of

Latest version
0.2.3
Last published
First published
Releases
4
License (package)
MIT
Direct dependencies
10
Unpacked size
43 KB
Registry signature
Not measured
Build provenance
No attestation

How was this verified, and what are the sources?

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

  1. Official MCP Registry record for com.feeless402/nano-pay at version 0.2.2 - lists package pypi:feeless402 and repository https://github.com/feeless402/feeless402 - accessed
  2. PyPI metadata for feeless402 at published version 0.2.3, retrieved 2026-08-20 - declares a dependency on mcp, which resolves to mcp@2.0.0 - accessed
  3. Published artifact of mcp@2.0.0, retrieved 2026-08-20 - the artifact states no ceiling constant, declares revision 2026-07-28 and implements the stateless server/discover method. Read from the artifact itself, not from release notes - accessed