mcp-metsuke-crunchtools
OfficialThis server is a stateful MCP reports catalog that lets agents define what to gather, trigger and persist cited findings, and read them back for compilation.
Manage report definitions – create or update reports with name, gather prompt, owner agent, cron schedule, timezone, and source config (
upsert_definition).List report catalog – view all definitions with prompts, owners, schedules, source configs, and update times (
list_reports).Inspect a report spec – fetch the full gather prompt and source configuration for a named report (
get_spec).Trigger gathering on demand – fire a report immediately without waiting for the cron schedule (
trigger_report).Save gathered outputs – persist findings as an array of objects, each ideally carrying a source URL, with status, window times, and gatherer run reference (
save_output).Read outputs for compilation – retrieve the freshest output or the latest output for a specific date (
get_output).Built-in scheduler – automatically fires report gathers according to cron schedules when running under SSE or streamable-http transports.
Multiple transports – supports stdio, SSE, and streamable-http for flexible agent integration.
Local-first storage – stores everything in a plain SQLite database (WAL mode) with no external services required.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-metsuke-crunchtoolspull the freshest output for the 'weekly vuln scan' report"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-metsuke-crunchtools
Stateful reports catalog MCP server. Metsuke (目付 — the Sengoku intelligence officer who gathered field reports and compiled them for the daimyō) is the durable, cross-agent home for report definitions and their gathered outputs.
An autonomous gatherer reads a definition, sweeps the configured sources, and writes findings — each carrying its own source URL. A compiler later reads the freshest output to draft a fully cited report. This replaces ad-hoc, run-scoped research caches with a real, queryable store.
Features
Definitions + outputs — separate what-to-gather from what-was-gathered
Built-in scheduler — Metsuke fires each definition's gather when its cron schedule comes due, or on demand via
trigger_report— no external timerCited findings — payloads carry per-finding source URLs for one-click checking
Re-homeable gathering —
owner_agentmakes the gatherer identity data, not codeLocal-first — plain SQLite (WAL), no external services, no per-seat fees
Three transports — stdio, SSE, streamable-http
Related MCP server: arcane
Install
uvx (recommended)
uvx mcp-metsuke-crunchtoolspip
pip install mcp-metsuke-crunchtoolsContainer
podman run --rm -v ~/.local/share/mcp-metsuke:/data:Z \
quay.io/crunchtools/mcp-metsuke \
--transport streamable-http --host 0.0.0.0 --port 8009Claude Code Integration
claude mcp add mcp-metsuke-crunchtools -- uvx mcp-metsuke-crunchtoolsTools (6)
Definitions (4)
Tool | Description |
| List all report definitions in the catalog, each with its next scheduled fire time. |
| Return the gather prompt + source config for one definition. |
| Create or update a definition (name, prompt, owner, cron schedule, timezone, sources). |
| Fire a report gather right now, without waiting for its schedule. |
Outputs (2)
Tool | Description |
| Persist gathered findings for a report (each ideally carrying a source URL). |
| Read the freshest output (or a specific day's) for compiling a report. |
Environment Variables
Variable | Default | Description |
|
| SQLite database path |
| (none) | Path whose contents override |
| (none) | Base URL of the Trentina alert endpoint the scheduler POSTs gather callbacks to |
| (none) | Alert token identifying the reports profile; enables the scheduler when set with |
| (none) | Path whose contents override |
|
| How often the scheduler checks for due reports |
| (auto) | Force the scheduler on/off; defaults to on when the callback is configured |
The scheduler runs only under the sse and streamable-http transports (the long-lived production processes), never under stdio.
Data Model
report_definitions —
name(PK),gather_prompt,owner_agent,schedule(cron),timezone(IANA),source_config(JSON),last_fired_at,updated_atreport_outputs —
id,report_name(FK),gathered_at,window_start/window_end,payload(JSON findings with source URLs),status(gathering/ready/compiled),gatherer_run_ref
MCP Registry
io.github.crunchtools/metsuke
License
AGPL-3.0-or-later
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to autonomously manage and improve execution processes for repetitive task types by storing reusable task contexts with associated artifacts (practices, rules, prompts, learnings) and providing full-text search across historical best practices.81MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.MIT
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent memory across sessions, enabling recall of decisions, clients, and deadlines with verifiable citations.
- AlicenseNot gradedqualityCmaintenanceDurable, inspectable memory for MCP agents. Preserves decisions, preferences, and project knowledge across sessions with full provenance and version history.2Apache 2.0
Related MCP Connectors
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
A collaborative repository where AI agents and humans share research, images, videos and papers.
Cross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/crunchtools/mcp-metsuke'
If you have feedback or need assistance with the MCP directory API, please join our Discord server