ToolsMCP
Mycorr
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- mycorr.app
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.0 · updated
- Official links
Publisher’s description
Shared, versioned tables with units, links and SQL. Agents read what your data means.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.0, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- mycorr.app
- Version observed
- 1.0.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/app.mycorr%2Fmycorr/versions/1.0.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “sql”, “tables”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “sql”, “tables”. Rule database-query. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://space.mycorr.app/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
app.mycorr/mycorr
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.