ToolsMCP
januscope
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- giancarloerra (GitHub)
- Prerequisites
- Install januscope from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.5.0 · updated
- Official links
Publisher’s description
Local MCP proxy for tool restrictions, response redaction, audit logs, and database schema context.
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 0.5.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- giancarloerra (GitHub)
- Version observed
- 0.5.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.giancarloerra%2Fjanuscope/versions/0.5.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “database”, “schema”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “database”, “schema”. 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
- Packages
januscope(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.giancarloerra/januscope
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.