github-repo-shape — UTC second MCP Tool
github-repo-shape
(github repo shape) is one of 31 tools on the
UTC second
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call github-repo-shape from your client
- Claude Code UTC second github-repo-shape run in your project directory
- Claude Desktop UTC second github-repo-shape ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor UTC second github-repo-shape ~/.cursor/mcp.json
- VS Code UTC second github-repo-shape .vscode/mcp.json
- Zed UTC second github-repo-shape ~/.config/zed/settings.json
- Windsurf UTC second github-repo-shape ~/.codeium/windsurf/mcp_config.json
- Cline UTC second github-repo-shape ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI UTC second github-repo-shape ~/.gemini/settings.json
- Grok UTC second github-repo-shape .mcp.json (in your project root)
- ChatGPT UTC second github-repo-shape Settings → Connectors → Advanced → Developer mode
- Claude.ai UTC second github-repo-shape Settings → Connectors → Add custom connector
- LangChain UTC second github-repo-shape pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http second-utc https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/second-utc/mcp
Other tools on this server
- second-utc
- utc-time
- timezone
- validate-json
- normalize-url
- inspect-robots
- domain-shape
- citation
- compatibility
- status-catalog
- iana-zones
- web-fetch
- fetch-status
- weather-hint
- memory-key-count
- file-path-ok
- browser-url-ok
- think-steps
- search-query-len
- hn-front-count
- lib-docs-hint
- playwright-url-ok
- figma-url-shape
- jira-key-shape
- geo-hint
- calc-eval
- wiki-title-ok
- agent-tool-index
- people-search-index
- agent-ads-index
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.