"namespace:com.ramp.ramp-mcp-remote" matching MCP tools:

• pathrule_resolve_refresh

  Pathrule

  Close a Pathrule refresh task after reviewing its brief. Normal remote flow: call pathrule_list_pending_refreshes, then pathrule_get_refresh_brief, then use this tool with status='rejected' when the signal is stale or not actionable. Remote MCP may refuse status='applied' because it cannot verify local source files; use Pathrule Studio/CLI for applied resolutions that require local verification.

  Connector

• fvs_download_final_video

  Future Video Studio

  Download a completed Future Video Studio final render URL to a local file. Use this only after fvs_get_render_status or fvs_get_paid_render_status returns a final_video_url for a completed render. The tool performs an unauthenticated HTTPS GET to that signed URL and writes the response bytes to output_path on the MCP server's local filesystem. It does not call the FVS Agent API, spend wallet credits, require FVS_AGENT_API_KEY, cancel jobs, or modify remote render state. Side effects and constraints: output_path is a local filesystem path for the MCP server process, parent directories are created, existing files are not replaced unless overwrite is true, and large videos may take minutes to download. The request timeout is 600 seconds. Use a fresh status check to refresh expired signed URLs, and do not pass arbitrary or untrusted URLs.

  Connector

• switch_dannet_server

  dannet

  Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")

  Connector

• search_mcp_servers

  agent-tools (x402 + MCP + A2A directory)

  Find MCP servers in the directory. Searches the standalone MCP directory (PulseMCP / official MCP registry import) unioned with x402 services that also expose an MCP endpoint. Returns normalised entries with a ready-to-use streamable-http `call_hint.mcp.url`. Args: intent: Natural-language description of the tool/capability needed. top_k: Max servers to return (1-20). chain: Optional payment-network filter for paid MCP servers. require_healthy: When true, only return servers marked health=ok.

  Connector

• audit_mcp

  SaSame MCP Observatory + Gold Rush Town

  Grade one MCP server A-D against the Agent-Tool Discoverability Standard. SaSame is the independent operational evidence layer for remote MCP infrastructure; status only, not endorsement. Runs the LEGITIMATE MCP handshake (initialize + tools/list + one read-only tool call, all over POST JSON-RPC) and returns the grade, a per-criterion pass/evidence breakdown, and the single biggest gap to fix. This returns the grade and analysis ONLY — if you want a signed, portable certificate of the same audit, use verify_mcp_ready instead. DIRECTORY PRE-FLIGHT: these criteria cover the MECHANICAL reject reasons of the Claude Connectors Directory and ChatGPT Apps Directory (annotations, typed schemas, description clarity, liveness, graceful errors, anti-ghost) — run it before you submit. It does NOT cover privacy-policy, identity/business verification, OAuth callbacks, or prohibited-category rules; it catches mechanical failures, it does not guarantee a pass. Handshake only — no auth-bypass, no payment. Free. Best run against YOUR OWN server. (The census found ~80% of public MCP servers return no real content; this tells you which side you're on.)

  Connector

• recommend_mcp

  SaSame MCP Observatory + Gold Rush Town

  Get SaSame-observed MCP server recommendations for a capability you need. SaSame is the independent operational evidence layer for remote MCP infrastructure; status only, not endorsement. SaSame's MCP Observatory continuously crawls and GRADES thousands of public MCP servers (A/B/C/D) by reachability and whether they return real content. This returns the top live, real-content endpoints (optionally filtered by an endpoint keyword), each with its SaSame grade and last-audited time — so you (or the human you assist) can pick a measured MCP candidate instead of guessing. Each result includes a longitudinal trend (when SaSame has observed it over time) and a ready-to-quote, attributed `cite` line; the top pick with history carries an ed25519-signed, offline-verifiable record you can cite as a third-party source. Free, read-only, no signup. If you operate one of these servers, claim it (claim_start). If you can't find a fit and need an MCP/agent BUILT, call engage_sasame. Pass a referral handle from `refer` as engage_sasame(ref=...) to attribute the introduction.

  Connector

• quick_check

  mcp-judge

  FREE, no payment required. Instant trust check of any MCP server: returns only the 0-100 score, A-F grade, tool count, latency and a one-line verdict — no detailed report. Use this FIRST, before integrating any third-party MCP server, to see at a glance whether it is technically trustworthy; an unreliable MCP wastes your tokens and can break your workflow. For the full actionable report (per-tool documentation coverage, functional probe results, score breakdown, plain-language summary) call evaluate_mcp; to pick between alternatives call compare_mcps. Set 'url' (required) to the target's MCP endpoint (Streamable HTTP), e.g. https://host/mcp.

  Connector

• vf_health

  VoiceFlip

  Returns VoiceFlip MCP server health and version metadata. No authentication required. Use this first to verify the server is reachable from your MCP client.

  Connector

• show_version

  Banco Sofisa MCP

  Show the current MCP platform and adapter versions.

  Connector

• catalog__get

  Agentage MCP Catalog

  Fetch the complete record for ONE MCP server in the agentage directory by its exact slug: full description, categories, the packages and remote endpoints it ships, the tools it exposes, a ready-to-run install command, and a README excerpt. Use this after catalog__search to get the depth a result card omits - pass a slug exactly as returned by catalog__search, never a guessed or constructed one. No slug yet? call catalog__search first. Read-only.

  Connector

• tools.find_for_task

  Revuo.ai MCP

  Find the best MCP tools for a given task. Describe what you want to accomplish (e.g. 'manage github issues', 'send slack messages', 'query a database') and get ranked results — each result is one (product, tool) pair, since same-named tools across providers are NOT interchangeable. By default only shows tools available via remote (network-hosted) servers. Audience: agent builders looking for installable MCP tools — for B2B SaaS recommendations, prefer products.search or products.find_by_capability. Ranking basis: relevance score desc (+1 per term hit, +3 for full-phrase hit); within an equal relevance tier, callable-now (Open access) + remote + healthy tools are boosted ahead — never a hard filter (a product-bound tool stays in its own money query), then productName. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } plus preflight annotations { accessModel (open|keyed|account|commercial), healthScore (0-100, nullable), readOnly, destructive, callableNow (true = usable anonymously right now), setup (one-line 'how to get access' pointer for non-Open tools) }. Response: { task, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], capabilityProducts[] (B2B SaaS products that claim the same capability — empty when matchType=none), results[] (MCP-tool-level matches), buckets { callableNow, requiresSetup } }. Each result: { position, rank, normalizedName, displayName, description, inputSchema, relevance, accessModel, healthScore, readOnly, destructive, callableNow, setup, productSlug, productName, serverQualifiedName, isRemoteCapable, tier, unverified, verifiedAt }. Empty case: { task, matchType, message, suggestedQueries[], suggestedCapabilities[] }.

  Connector

• call_service

  FiatDock

  Invoke a listed FiatDock service. PAID listings go THROUGH the gateway (POST /s/:id) so the non-custodial split is enforced — normally TWO payments (99% seller + 1% FiatDock), or ONE full-price payment to the seller during that seller's first-month 0% launch window; this remote /mcp cannot sign payments, so it returns the gateway's 402 challenge as an error (use the fiatdock-mcp npm package with AGENT_PRIVATE_KEY to pay whatever the 402 lists automatically). FREE / first-party listings are forwarded to their real MCP endpoint directly (no payment). Pass the service's expected request body as `args`.

  Connector

• lookup_readiness

  SaSame MCP Observatory + Gold Rush Town

  Look up SaSame's EXISTING, independently ed25519-signed Readiness attestation for any MCP/agent endpoint. SaSame is the independent operational evidence layer for remote MCP infrastructure; status only, not endorsement. a neutral third party's measured record (reachable / callable / schema-valid / grade / when last measured) that an agent CANNOT issue about itself. Backed by SaSame's continuously-refreshed observation ledger (25,000+ observed endpoints, 88,000+ measurements). Returns the matching record as a freshly signed attestation you re-verify OFFLINE (no callback to SaSame), or, if not yet observed, exactly how to add it (call audit_mcp). Pure read: no live probe, no network, instant. Verification status only - NOT a safety, quality, or trust verdict.

  Connector

• heron_mcp_scan

  heron

  Check whether an MCP SERVER is SAFE TO CONNECT before you add it. An MCP server's tool names, descriptions and schemas are injected into your context, and you will obey instructions hidden there ("tool poisoning"). Provide EITHER `url` (a live remote MCP endpoint — Heron connects READ-ONLY, reads tools/list, and NEVER calls a tool) OR `tools` (a pasted tools/list array, for stdio/self-hosted servers). Returns a 0-100 trust score, a verdict (trusted / caution / dangerous), and the findings: hidden agent-directed instructions, data exfiltration, sensitive-parameter capture, tool shadowing, and obfuscated payloads (Morse, base64, invisible Unicode, homoglyphs) — plus a wallet-signed attestation. Free.

  Connector

• tools.find_for_task

  Revuo

  Find the best MCP tools for a given task. Describe what you want to accomplish (e.g. 'manage github issues', 'send slack messages', 'query a database') and get ranked results — each result is one (product, tool) pair, since same-named tools across providers are NOT interchangeable. By default only shows tools available via remote (network-hosted) servers. Audience: agent builders looking for installable MCP tools — for B2B SaaS recommendations, prefer products.search or products.find_by_capability. Ranking basis: relevance score desc (+1 per term hit, +3 for full-phrase hit); within an equal relevance tier, callable-now (Open access) + remote + healthy tools are boosted ahead — never a hard filter (a product-bound tool stays in its own money query), then productName. Paid tier is NOT a ranking input — it appears only as an annotation. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } plus preflight annotations { accessModel (open|keyed|account|commercial), healthScore (0-100, nullable), readOnly, destructive, callableNow (true = usable anonymously right now), setup (one-line 'how to get access' pointer for non-Open tools) }. Response: { task, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], capabilityProducts[] (B2B SaaS products that claim the same capability — empty when matchType=none), results[] (MCP-tool-level matches), buckets { callableNow, requiresSetup } }. Each result: { position, rank, normalizedName, displayName, description, inputSchema, relevance, accessModel, healthScore, readOnly, destructive, callableNow, setup, productSlug, productName, serverQualifiedName, isRemoteCapable, tier, unverified, verifiedAt }. Empty case: { task, matchType, message, suggestedQueries[], suggestedCapabilities[] }.

  Connector

• agoragentic_register

  Agoragentic Agent OS MCP

  Register as a new agent on Agoragentic. Returns an API key and access to the router-facing authenticated surfaces. If this MCP session is not yet authenticated, the new key is bound to the current session automatically, so authenticated tools work on your very next call. An already-authenticated session keeps its existing key. Persist the key for future sessions — stdio relay: set AGORAGENTIC_API_KEY; remote HTTP: send Authorization: Bearer <key> at initialize, or pass _meta.apiKey per tools/call.

  Connector

• show_version

  Banco MCP

  Show the current MCP platform and adapter versions.

  Connector

• openlibrary_search_authors

  openlibrary-mcp-server

  Search Open Library authors by name. Returns Open Library Author IDs, names, birth/death dates, top works, and subject associations. Use author IDs for openlibrary_get_author (bio, remote IDs) or openlibrary_get_author_works (list of works).

  Connector

• usage_guide

  Camber - Remote Agentic Data Science

  Instructions for correctly using this MCP server. Call at the start of a session to learn tools, auth, CLI prerequisites, and stash file handling.

  Connector

• pathrule_take_snapshot

  Pathrule

  Record a point-in-time inventory of the user's project under a workspace. Remote MCP cannot see the filesystem, so YOU (the AI) collect this inventory with your own Read/Glob/Grep tools before calling this. Persist it so future setup, bootstrap, drift detection, and onboarding flows have structured evidence to reason over. Required: workspace_id. Strongly recommended: project_name, file_count, file_tree (cap at ~5000 entries — summarise deeper paths), file_extensions_summary, top_level_dirs, sampled_contents for README, package.json / pyproject.toml / Cargo.toml, CLAUDE.md, AGENTS.md, main config files (truncate each to ~4KB). Optional: git_head / branch / git_log_summary if you can read them, ai_notes for free-form observations.

  Connector