# ogfetch (remote · ogfetch.dev)

URL to JSON metadata: title, Open Graph, favicon, tech stack. Agents self-signup and pay in USDC.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ogfetch.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp.md), [page](https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp)

## Channel facts

- Endpoint: `https://ogfetch.dev/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 799 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-ogfetch-ogfetch 'https://ogfetch.dev/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-ogfetch-ogfetch": {
      "url": "https://ogfetch.dev/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-ogfetch-ogfetch": {
      "type": "http",
      "url": "https://ogfetch.dev/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-ogfetch-ogfetch]
url = "https://ogfetch.dev/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-ogfetch-ogfetch": {
      "type": "remote",
      "url": "https://ogfetch.dev/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-ogfetch-ogfetch --url 'https://ogfetch.dev/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-ogfetch-ogfetch:
    url: "https://ogfetch.dev/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-ogfetch-ogfetch": {
      "Transport": "http",
      "Url": "https://ogfetch.dev/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-ogfetch-ogfetch -t streamable-http -u 'https://ogfetch.dev/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-ogfetch-ogfetch": {
      "type": "http",
      "url": "https://ogfetch.dev/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 66, +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.

### 2026-11-04 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 65)

First indexed and scored.

## MCP tools (7)

### `fetch_url_metadata` (~144 tokens)

Fetch URL metadata

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.

Input parameters:

- `api_key` (string): Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header.
- `url` (string, required): Absolute http(s) URL to fetch, e.g. https://github.com

### `create_account` (~87 tokens)

Create ogfetch account

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.

Input parameters:

- `contact` (string): Optional contact (email or URL) for the operator.
- `name` (string): Optional label for the agent or app using this key.

### `get_account` (~50 tokens)

Get credit balance

Return the remaining credit balance and usage for the API key.

Input parameters:

- `api_key` (string): Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header.

### `get_pricing` (~23 tokens)

Get pricing

List available one-time credit packs and prices. No API key needed.

### `buy_credits` (~121 tokens)

Buy credits

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.

Input parameters:

- `api_key` (string): Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header.
- `plan` (string, required): Credit pack to buy.

### `buy_credits_usdc` (~146 tokens)

Buy credits with USDC (Solana Pay)

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.

Input parameters:

- `api_key` (string): Your ogfetch API key (ogf_...). Optional if the MCP connection is already configured with an Authorization header.
- `plan` (string, required): Credit pack to buy.

### `check_usdc_payment` (~64 tokens)

Check USDC payment

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.

Input parameters:

- `reference` (string, required): The reference from buy_credits_usdc.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp#diagnostics

## Score history

- 2026-11-05: 66
- 2026-11-04: 65
- 2026-11-03: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://ogfetch.dev/v1/mcp
- Website: https://ogfetch.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-ogfetch-ogfetch/v1-mcp