@gravv/mcp
OfficialRelated Servers
Alternatives to @gravv/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for the Monei API that gives AI agents access to wallets, transfers, crypto sends, swaps, offramp, and bill payments through natural language.2420 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for ClawVault - an AI agent payment security layer that enables Claude to request payments, check limits, and manage transactions with configurable rules.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.112 npm1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to safely interact with a double-entry payments ledger, enforcing idempotency, policy-based access control, and human-in-the-loop approval for high-value actions.-
- FlicenseNot gradedqualityDmaintenanceAn experimental MCP server that lets AI agents interact with guarded payment workflows through typed tools, enabling safe agent-assisted payments with M-Pesa and mock Airtel Money.3-
- FlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI agents interact with the Adaptis (MEG) payment gateway, enabling payment link creation, transaction queries, refunds, and integration helpers like generating signed forms and verifying callbacks.-
TDQS
Scored across 2 tools
The two tools form the classic search-then-fetch pair with clearly disjoint roles: one returns ranked excerpts across the docs corpus, the other returns full text for a single slug returned by the first. The descriptions explicitly state the handoff ("follow up with getGravvDocPage" / "by slug, as returned by searchGravvDocs"), leaving no room for misselection.
Both names follow the same camelCase verb+noun pattern with a shared Gravv/Doc domain prefix: searchGravvDocs and getGravvDocPage. The verbs (search vs get) correctly signal breadth vs single-item retrieval, so the convention is both predictable and semantically informative.
Two tools is thin relative to the 3-15 guideline, but for a pure documentation-retrieval server the search/fetch pair is the minimal complete surface and neither tool is redundant. Nothing is padded, though a third tool (e.g. list/index pages) would round it out.
Search plus full-page fetch covers the documentation lookup lifecycle end to end, including the excerpt-to-full-text escalation path. The only minor gap is the absence of any way to browse or enumerate page slugs or check docs versioning without a prior search hit.