RMCP.DEV
← pubfi.ai

INDIVIDUAL MCP TOOL

pubfi.route.execute

Execute one exact GET or POST path through the same Registry v2 matcher, credential authority, and typed executor as the HTTP gateway.

pubfi.ainone authenticationAvailability not checked

Input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.
  • A tool name or description suggests code or command execution.
  • A tool name, description or schema mentions credentials.

Parent endpoint

pubfi.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pubfi-rust-mcp]
url = "https://mcp.pubfi.ai"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "pubfi-rust-mcp": {
      "type": "http",
      "url": "https://mcp.pubfi.ai"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: pubfi-rust-mcp
Remote MCP URL: https://mcp.pubfi.ai

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pubfi-rust-mcp": {
      "url": "https://mcp.pubfi.ai"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "pubfi-rust-mcp": {
      "type": "http",
      "url": "https://mcp.pubfi.ai"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "pubfi-rust-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.pubfi.ai"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • pubfi.capabilities.search — Search the currently installed Registry v2 capability snapshot without querying PostgreSQL, the Control Plane, or upstream providers.
  • pubfi.route.plan — Plan an exact Registry v2 route from the installed in-memory generation without executing an upstream request or creating usage.
  • pubfi.route.explain — Explain a route decision using only the currently installed Registry v2 catalog and its exact generation and manifest identity.
  • pubfi.schema.get — Return the current Registry-aware MCP input and output schema for a named tool, including the installed generation and dynamic routes.