MCP feature support

This page lists the MCP features the shared connection supports, https://link.mcpmarket.com/mcp. They work the same in Everything and in a single toolkit, whether you sign in or use an API key.

Most features need support from your MCP client and from the MCP server that provides them. A feature listed here is unavailable when either side doesn't support it, and support varies between clients. Check your client's documentation.

Feature support

A current client uses MCP version 2026-07-28. Clients on an earlier version, such as 2025-11-25, get tools, plus skill-reading tools for your MCP Market skills, and nothing else on this page.

Every feature follows your current access. Resources, prompts, and skills come only from MCP servers included in your selection, and never give access to a tool you didn't select. When you lose access, they stop working.

Tools

Tools work in every MCP client. Large Everything catalogs provide search and invoke tools for finding tools on demand. See Connect a toolkit view to choose what the connection shows.

Skills

Clients that support native MCP skills discover your MCP Market skills and the skills of your MCP servers together. Other clients read skills through skill-reading tools.

• An MCP server's skill may name that server's tools by their original names. MCP Market can list those tools under different names, so your agent may need to match them.
• A skill file too large for tool delivery is refused whole, never cut short. Read it with a client that supports native skills or resources.
• Skill-reading tools can't answer an MCP server's input requests. Use a client with native skills or resources for those skills.

See Connect a toolkit to check a skill's delivery.

Resources, prompts, and completion

• Resources and templates are listed from the MCP servers in your selection. Resource links in tool results and prompts stay readable through the connection.
• Prompt names start with a prefix for their MCP server, so prompts from different servers never collide.
• Completion suggests prompt and template arguments. Suggestions come from the MCP server; MCP Market doesn't generate them.
• Failures are reported, not hidden. If an MCP server fails while listing, the request returns an error naming it instead of an incomplete list. Try again.
• Size limit. A resource or prompt response larger than 16 MiB is refused whole, never cut short. The limit includes encoding, so a binary file over about 12 MiB is refused.

Input requests

An MCP server can ask you for information, or send you to a web page, during a tool call, resource read, or prompt request. Your client shows the request, and your answer resumes the same call.

An MCP server can ask only when your client supports input requests and the MCP server's connection supports interactive requests. Otherwise the MCP server handles the call without asking you.

Custom MCP servers you deploy on MCP Market don't send input requests. This doesn't affect MCP Market's own connection prompts, described below.

• Answer within 15 minutes. After that, make the request again.
• Declining or cancelling ends the call.
• If a tool call needs a connection that you can set up or repair, clients that support web page requests send you to the page in MCP Market. Otherwise, such as for a shared connection when you're a member, you're told an admin needs to fix it. Resource reads and prompt requests return a connection error instead.
• MCP servers on an earlier MCP version can't send input requests through MCP Market.

Logs

Logs are opt-in for each request. When your client sets a log level, supported messages at that level or higher arrive with the response. Without a level, no log messages are sent.

MCP Market drops messages it cannot safely associate with your request. This includes ambiguous logs from concurrent requests to a custom MCP server deployed on MCP Market.

MCP Market relays logs but doesn't store them. The current MCP specification deprecates logging, and MCP Market keeps it for compatibility. Setting a log level for a whole session isn't supported, and logs never arrive on change notification streams.

Change notifications

Current clients can subscribe to changes. When a subscription opens, your client learns which of its requested notifications it will receive.

• Tool list changes are always available. They report changes to the tools MCP Market shows you, within about 30 seconds.
• Prompt and resource list changes are available only when every connected MCP server in your selection, and its connection, supports them.
• Resource updates are available for each resource whose MCP server and connection support them.
• MCP servers on an earlier MCP version don't send change notifications through MCP Market.
• Skill changes aren't notified, including skill-reading tools from MCP servers.

You can keep two subscriptions open per account, shared across all of your signed-in connections and API keys. Missed notifications aren't replayed. A subscription can end, for example after a disconnect or when your access changes. Subscribe again and refresh your lists.

Tasks

Tasks are not generally available. On a connection without Tasks, a client that supports them gets each tool's result directly, like any other client.

Where Tasks are available, a long-running tool call from an MCP server that supports Tasks returns a task your client can check after disconnecting. Your client can check its status, answer its input requests, and request cancellation. Supporting clients can also subscribe to task updates and receive the result through Events. Task handles expire after 30 days without client activity, or earlier if the MCP server's task expires. An active task subscription keeps the handle in use. The MCP server may still finish the work after a cancellation request. Listing tasks and the earlier 2025-11-25 form of Tasks aren't supported, and neither are Tasks for custom MCP servers you deploy on MCP Market.

MCP Apps

MCP Apps aren't supported. MCP Market doesn't offer App interfaces to clients, even when an MCP server provides one. That server's tools remain available as ordinary tools.

Older connection URLs

This page covers the shared connection only. Older per-toolkit connection URLs and individual MCP server endpoint URLs keep their existing behavior. To use the features above, replace the URL with the shared connection from Connect and reconnect.

Usage

Only tool calls count toward your included tool calls. A tool call counts once however many input requests it makes, and a task counts once when your client checks or receives its final status. If your client leaves and never observes the final status, that task does not count. MCP Market does not independently poll abandoned tasks. Resources, prompts, completion, skill reads, logs, and change notifications don't count as tool calls. Rate limits apply to every request.

Related