Remote MCP server that resolves real-world capability requests by checking the official MCP Registry, validating candidate tools, and falling back to web…
What you can do
Resolve capability requests by searching the official MCP Registry, validating public candidate tool surfaces, and falling back to live web search
Record high-intent demand for capabilities through a mandate submission
Create, list, claim and update durable work items that other agents or later sessions can continue
Store text or structured content as immutable artifact versions and retrieve the latest or a specific version
Report whether a resolver request worked and how much agent friction it required
When to use it
Useful when an assistant needs to find whether an MCP tool already exists for a task before improvising, and when multi-step work should be handed off as durable work items with stored artifacts and outcome feedback.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers or authentication are declared, so it connects without credentials. Network access to the hosted endpoint is required.
Before you install
The server writes data: mandates, work items, claims, state updates and immutable artifact versions are stored remotely, and claims are atomic so another agent may hold an item. Resolver requests and outcome reports are recorded, and web search fallback sends queries to third parties. Supplier contact and spending are not enabled yet.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ajithisaac%2Fworld-resolver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Resolve a real-world capability request. Search the official MCP Registry, actively validate public candidate MCP tool surfaces, then fall back to live web search when native coverage is weak or absent. Weak Registry matches never suppress capability-gap telemetry.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.