InfinitePay MCP

marketplace

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.

Input Schema

TableJSON Schema

Name	Required	Default
`limit`	No
`query`	No
`action`	No	search
`mcp_id`	No
`message`	No
`tool_id`	No
`arguments`	No	{}
`immediate`	No
`tier_slug`	No
`prompt_body`	No
`prompt_slug`	No
`prompt_tool`	No
`prompt_vars`	No	{}
`conversation`	No	[]
`prompt_title`	No
`request_name`	No
`cancel_reason`	No
`cancel_comment`	No
`prompt_targets`	No
`report_context`	No
`prompt_category`	No
`request_details`	No
`prompt_description`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedAug 26, 2026
RemovedAug 26, 2026

Changed9 schema fields changedAug 10, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "resume",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke",
+  "search_prompts",
+  "get_prompt",
+  "publish_prompt"
+]

addedInput schema / properties / prompt_body

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_category

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_description

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_slug

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_targets

Added value: +{
+  "default": [],
+  "items": {
+    "enum": [
+      "claude",
+      "chatgpt",
+      "cursor",
+      "lovable"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / prompt_title

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_tool

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / prompt_vars

Added value: +{
+  "default": "{}",
+  "type": "string"
+}

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "describe",
-  "install",
-  "uninstall",
-  "subscribe",
-  "cancel",
-  "report_bug",
-  "request_mcp",
-  "list_tools",
-  "invoke"
-]New value: +[
+  "search",
+  "describe",
+  "install",
+  "uninstall",
+  "subscribe",
+  "cancel",
+  "resume",
+  "report_bug",
+  "request_mcp",
+  "list_tools",
+  "invoke"
+]

Changed2 schema fields changedJul 10, 2026

addedInput schema / properties / cancel_comment

Added value: +{
+  "default": "",
+  "type": "string"
+}

addedInput schema / properties / cancel_reason

Added value: +{
+  "enum": [
+    "too_expensive",
+    "missing_features",
+    "switched_service",
+    "unused",
+    "customer_service",
+    "too_complex",
+    "low_quality",
+    "other"
+  ],
+  "type": "string"
+}

AddedJun 30, 2026
RemovedJun 22, 2026
First observedJun 11, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses side effects and behaviors beyond annotations: invoke runs one-off without permanently adding the MCP, returns connect/checkout links, write operations require workspace owner/admin, and prompt links open without login. No contradiction with annotations (readOnlyHint=false, openWorldHint=true).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is an extremely long, single paragraph with dense run-on sentences. While every sentence adds information, the lack of bullet points, section breaks, or clear separation of sub-flows makes it hard to parse. It is over-sized and poorly structured for an AI agent to quickly extract guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite missing description for a few enum values (resume, tier_slug) and some params, the description covers the core search→describe→invoke flow, install/uninstall, billing, permissions, prompt library, and error/edge-case behaviors. For a highly complex tool with no output schema, this is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the action parameter and key params like tool_id, arguments, mcp_id, and prompt_*, but with 23 params and zero schema coverage it leaves many undocumented (limit, query, message, immediate, tier_slug, conversation, cancel_reason, cancel_comment, prompt_targets, report_context, request_details, etc.). Names provide some self-evidence, but the description only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as the mcp.ai marketplace, explicitly covering capability requests, discovery, running MCPs, and the prompt library. It uses specific verbs and resources (search, describe, invoke, install, list_tools, subscribe/cancel) and stands apart from sibling openfinance tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'prefer invoke for a single/occasional use', 'Use install only to make an MCP PERMANENT', and contrasts with list_tools, subscribe/cancel, report_bug, and request_mcp. It even covers edge cases like missing credentials and empty wallets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InfinitePay MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

marketplace

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources