Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.CedricKouma/fetch-extract

REMOTE · APIM-AGENTFORGE-6LFM33.AZURE-API.NET · 2 COMPONENTS · SCANNED AUG 3

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

+10 this week 28 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security71
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · apim-agentforge-6lfm33.azure-api.net

# add to Claude Code
claude mcp add --transport http cedrickouma-fetch-extract https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp
# ~/.codex/config.toml
[mcp_servers.cedrickouma-fetch-extract]
url = "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cedrickouma-fetch-extract": {
      "type": "remote",
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cedrickouma-fetch-extract --url https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cedrickouma-fetch-extract:
    url: "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
// mcp.json
{
  "mcpServers": {
    "cedrickouma-fetch-extract": {
      "type": "http",
      "url": "https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp"
    }
  }
}

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

Changelog

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.

  • 31 Jul 26 +10
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 18

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.azure-api.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US 7 Jun 2026 4 Dec 2026 RSA 2048 SHA384-RSA 43004e30bc9e8ab33fadbd1bca0000004e30bc
SANs: *.azure-api.net, *.portal.azure-api.net, *.management.azure-api.net, *.scm.azure-api.net, *.configuration.azure-api.net, *.regional.azure-api.net, *.developer.azure-api.net, *.data.azure-api.net, *.portal-editor.azure-api.net, *.unique.azure-api.net, *.unique.portal.azure-api.net, *.unique.management.azure-api.net and 6 more
CN=Microsoft TLS G2 RSA CA OCSP 04,O=Microsoft Corporation,C=US (CA) CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US 1 Aug 2025 3 Jun 2029 RSA 4096 SHA384-RSA 330000000b13e5667d4a9b558000000000000b
CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 21 May 2025 19 Jun 2029 RSA 4096 SHA384-RSA b0c6b2c466917b04773c647d4afc0c8
DNSSEC insecure

Validation of apim-agentforge-6lfm33.azure-api.net. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
azure-api.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/fetch-extract",name="Ocp-Apim-Subscription-Key",type="header"

AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/fetch-extract",name="Ocp-Apim-Subscription-Key",type="header"
Header Value
www-authenticate AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/fetch-extract",name="Ocp-Apim-Subscription-Key",type="header"

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp Auth required 401
http (plaintext) http://apim-agentforge-6lfm33.azure-api.net/fetch-extract/mcp Inconclusive 404
MCP tools

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.

No tool schema has been captured from this endpoint yet.