Developer · Local MCP server
Tools MCP
MCP tools: WCAG contrast, JP char/X-weight count, WebP convert, JSON-LD, llms.txt.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.First-CH/tools-mcp- Version
- 0.4.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-20
- Updated
- 2026-07-20
- Publisher
- First-CH (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/First-CH) · how
- Repository
- github.com/First-CH/firstch-tools-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @first-ch/tools-mcp | 0.4.1 | stdio |
How to connect Tools MCP
Tools MCP runs locally from a Node.js package published to the npm registry: @first-ch/tools-mcp version 0.4.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @first-ch/tools-mcp@0.4.1. It reads the environment variable FIRSTCH_TOOLS_USAGE_LOG; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tools-mcp": {
"command": "npx",
"args": [
"-y",
"@first-ch/tools-mcp@0.4.1"
],
"env": {
"FIRSTCH_TOOLS_USAGE_LOG": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ToolgovernWraps the toolgovern CLI as a single generic MCP tool for agent-tool policy validation. | Local · stdio |
| ToolmeshSelf-hosted MCP gateway. Turn any REST API into MCP tools via YAML (DADL). Authz, audit, policies. | Remote · HTTP |
| ToolPipe MCP Server238+ dev tools via MCP: JSON, QR, PDF, DNS, hash, UUID, code review, JWT, SSL, WHOIS, and more. | Remote · HTTPLive check: ✗ no handshake |
| ToolrouteRoute AI agent tasks to MCP server and LLM, scored on 132+ real benchmark executions. | Local · stdio |
| ToolTrust ScannerScans MCP servers for prompt injection, data exfiltration, and privilege escalation. | Local · stdio |
| toolweaveOne MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers. | Remote · HTTPLive check: sign-in required |
| ToolYourRemote MCP: plan, run, verify for SEO/security/ship-gate. Same REST API key; 500 free credits/month. | Remote · HTTP, SSELive check: sign-in required |
| Toon MemoryOffline persistent memory for AI coding agents - 35 tools, 80% fewer calls, no LLM. | Local · stdio |