Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldTelnyxShortlist candidateCodebase Memory MCPMCP100 Recommended
Task fit
Best for
  • Telnyx users who want an MCP client to call supported Telnyx API actions and can scope a dedicated API key.
  • Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for
  • Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.
  • Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when
  • Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.
  • The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details

First-party MCP

endpoint:https: · Publisher source ↗

First-party MCP

DeusData · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Aug 14, 2026

Popularity evidence
GitHub starsNot documented

44,904

GitHub stars · checked 2026-09-25T18:35:00Z

Package downloads / 30 days

2,235

package downloads / 30 days · checked 2026-10-21

28,000

package downloads / 30 days · checked 2026-08-14T00:00:00.000Z

Shared repository stars

198

Shared repository stars (not MCP-specific) · checked 2026-10-21

Not documented
External adoption evidenceNot documented
  • npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationBearer Telnyx API key.local stdio; no remote auth needed
CostUnderlying Telnyx API/communications usage is billable according to the Telnyx account.none beyond local resources
PermissionsAuthority follows the exact Telnyx API key/account permissions; supported MCP actions may have real communications or account side effects.reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handlingRequests and Telnyx account/API data transit the hosted Telnyx MCP and connected AI client.local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs
  • Communications/account actions require stronger least-privilege and operational-safety evidence before Recommended.
  • Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed.
  • Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk contextCommunications/account actions require stronger least-privilege and operational-safety evidence before Recommended.latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review2026-10-212026-09-23
Candidate evidence2026-10-21T00:00:00Z2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →