ogfetch
REMOTE · OGFETCH.DEV
URL to JSON metadata: title, Open Graph, favicon, tech stack. Agents self-signup and pay in USDC.
Available components
Last scanned (6 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 799 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://ogfetch.dev/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ogfetch.dev | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 17 Jun 2026 | 31 Dec 2026 | RSA 2048 | SHA256-RSA | 3e1a49b645769306aa24a16190474ef |
| SANs: ogfetch.dev, www.ogfetch.dev | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ogfetch.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ogfetch.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ogfetch.dev/v1/mcp | Verified | 200 | |
| http (plaintext) | http://ogfetch.dev/v1/mcp | HTTPS enforced | 301 | https://ogfetch.dev/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buy_credits Buy credits ~121
Create a Stripe checkout link to top up this API key. Plans: starter = 1000 credits for $3; pro = 5000 credits for $10; business = 15000 credits for $20. Give the returned checkout_url to your user to pay (or complete it if you can make payments). Credits are added automatically after payment.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header. |
| plan | string | yes | Credit pack to buy. |
No output schema declared.
No examples provided.
buy_credits_usdc Buy credits with USDC (Solana Pay) ~146
Create a Solana Pay quote to top up this API key with USDC on Solana mainnet. Returns transaction_url, solana_pay_url, amount_usdc and a reference. POST {"account": "<your wallet address>"} to transaction_url to get a ready-to-sign base64 transaction; sign and send it. Or show solana_pay_url as a QR code for a human to scan in Phantom. Then call check_usdc_payment. No browser needed.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header. |
| plan | string | yes | Credit pack to buy. |
No output schema declared.
No examples provided.
check_usdc_payment Check USDC payment ~64
Check a buy_credits_usdc quote by its reference. Finds the payment on-chain and adds the credits once. Returns status pending, credited, or expired. Poll every few seconds after paying.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | The reference from buy_credits_usdc. |
No output schema declared.
No examples provided.
create_account Create ogfetch account ~87
Create a new ogfetch account with no email or browser required. Returns an API key with free trial credits. Only call this if you do not already have a key; store the returned key, it cannot be shown again.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional contact (email or URL) for the operator. |
| name | string | – | Optional label for the agent or app using this key. |
No output schema declared.
No examples provided.
fetch_url_metadata Fetch URL metadata ~144
Fetch a web page and return its metadata as JSON: title, description, canonical URL, favicon, Open Graph tags (og:title, og:image, ...), Twitter card tags, author/keywords/robots/theme-color, word count, HTTP status, response time, and detected tech stack (Next.js, WordPress, Shopify, Vercel, Cloudflare, ...). Costs 1 credit per successful fetch.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header. |
| url | string | yes | Absolute http(s) URL to fetch, e.g. https://github.com |
No output schema declared.
No examples provided.
get_account Get credit balance ~50
Return the remaining credit balance and usage for the API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header. |
No output schema declared.
No examples provided.
get_pricing Get pricing ~23
List available one-time credit packs and prices. No API key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ogfetch MCP server?
ogfetch is a hosted endpoint at https://ogfetch.dev/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ogfetch.dev
claude mcp add --transport http dev-ogfetch-ogfetch 'https://ogfetch.dev/v1/mcp'
What is the ogfetch MCP server?
ogfetch is an MCP server listed in the public MCP registry as dev.ogfetch/ogfetch. URL to JSON metadata: title, Open Graph, favicon, tech stack. Agents self-signup and pay in USDC. This page covers its hosted endpoint (https://ogfetch.dev/v1/mcp).
Is the ogfetch MCP server safe to use?
ogfetch scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ogfetch MCP server expose?
ogfetch exposes 7 tools: fetch_url_metadata, create_account, get_account, get_pricing, buy_credits, and 2 more. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.
Does the ogfetch MCP server require authentication?
No. We connected to ogfetch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ogfetch MCP server still maintained?
ogfetch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.