MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

rivemcp

Earlier Revision Publisher unverified Confidence: Good (0.85)

rivemcp is an MCP server published by paradoxsyn, 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 rivemcp support the current MCP specification (2026-07-28)?

Not yet confirmed. rivemcp 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 rivemcp a first-party (official) MCP server?

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

How do I connect to rivemcp?

rivemcp is available via the package npm:rivemcp, the official MCP Registry under io.github.paradoxsyn/rivemcp, the source repository at https://github.com/paradoxsyn/rivemcp-releases. Authentication: unknown. Transports: stdio.

Does rivemcp support MCP revision 2025-11-25?

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

Does rivemcp support MCP revision 2026-07-28?

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

When were rivemcp's facts last verified?

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

MCP server for creating and editing Rive (.riv) animation files. 139 tools for AI-driven animation.

Which MCP spec revisions does rivemcp support?

rivemcp 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 rivemcp?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for rivemcp

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

Stars
0
Forks
0
Last pushed
(40 days ago)
Created
Open issues
3
Primary language
JavaScript
Continuous integration
None detected
Tests
None detected
Security policy
None

Package (npm) as of

Latest version
1.13.5
Last published
First published
Releases
31
License (package)
SEE LICENSE IN LICENSE
Maintainers
1
Direct dependencies
10
Unpacked size
16 KB
Registry signature
Signed
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 io.github.paradoxsyn/rivemcp at version 1.0.5 - lists package npm:rivemcp and repository https://github.com/paradoxsyn/rivemcp-releases - accessed
  2. npm registry metadata for rivemcp at published version 1.13.2, 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