url-metadata__url_metadata — Fatstack MCP Tool
url-metadata__url_metadata
(url metadata url metadata) is one of 14 tools on the
Fatstack
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call url-metadata__url_metadata from your client
- Claude Code Fatstack url-metadata__url_metadata run in your project directory
- Claude Desktop Fatstack url-metadata__url_metadata ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fatstack url-metadata__url_metadata ~/.cursor/mcp.json
- VS Code Fatstack url-metadata__url_metadata .vscode/mcp.json
- Zed Fatstack url-metadata__url_metadata ~/.config/zed/settings.json
- Windsurf Fatstack url-metadata__url_metadata ~/.codeium/windsurf/mcp_config.json
- Cline Fatstack url-metadata__url_metadata ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fatstack url-metadata__url_metadata ~/.gemini/settings.json
- Grok Fatstack url-metadata__url_metadata .mcp.json (in your project root)
- ChatGPT Fatstack url-metadata__url_metadata Settings → Connectors → Advanced → Developer mode
- Claude.ai Fatstack url-metadata__url_metadata Settings → Connectors → Add custom connector
- LangChain Fatstack url-metadata__url_metadata pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http registry https://www.fatstack.net/api/mcp
Other tools on this server
- fatstack__free_demo
- echo__echo_json
- json-schema-validate__json_schema_validate
- html-to-markdown__html_to_markdown
- csv-to-json__csv_to_json
- text-language-detect__text_language_detect
- regex-test__regex_test
- unit-convert__unit_convert
- cron-explain__cron_explain
- uuid-batch__uuid_batch
- markdown-lint__markdown_lint
- askzephy-quick-scan__sol_audit
- askzephy-quick-scan__sol_quick_scan
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.