Developer Tools
rotifer.dev
A developer tool for searching Rotifer Protocol documentation, retrieving MCP configuration snippets, and suggesting matching domains from the Rotifer registry.
ENDPOINT 1
https://rotifer.dev
MCP server metadata
- Name
- WebMCP
Known tools 3
get_mcp_configGet Rotifer MCP Server configuration snippet for your Agent — returns a JSON config block you can add to your MCP client settings
Inferred read-onlysuggest_domainSuggest matching Gene domains from the Rotifer domain registry based on a description
Inferred read-onlyCONNECT 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.webmcp]
url = "https://rotifer.dev"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://rotifer.dev"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://rotifer.dev
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": {
"webmcp": {
"url": "https://rotifer.dev"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://rotifer.dev"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://rotifer.dev"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.