Is the Mcpscores Url Intel MCP server down?

mcp-registry/com.mcpscores/url-intel · v1.0.1

healthy
Last checked 2026-10-21 23:33 UTC · handshake 151ms

As of 2026-10-21 23:33 UTC, the Mcpscores Url Intel MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,188
outages (90d)
0
tools
5

Where a link really goes, what the server says about itself, and what pages a site publishes.

Install Mcpscores Url Intel MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mcpscores-url-intel-mcp-server https://url-intel.bowling-anthony.workers.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mcpscores-url-intel-mcp-server": {
      "type": "http",
      "url": "https://url-intel.bowling-anthony.workers.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 2 warning(s) across 5 tool(s); ~867 tokens of tool definitions.
Scores higher than 36% of 15,499 MCP servers Glimind has audited.
Its tool list costs an agent ~867 tokens per session — lighter than 80% of servers.
80 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints4
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: demand_report, request_data, resolve_url, site_pages, url_headers

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: site_pages

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mcpscores%2Furl-intel/fixes

resolve_url 1 change
{
  "name": "resolve_url",
  "description": "Follow a URL's redirect chain one hop at a time and report every step: each intermediate host and status, the final destination, whether it crossed to a different host, and a cleaned copy with tracking parameters (utm_*, fbclid, gclid and friends) stripped. Use before following or showing a shortened, tracked or unfamiliar link — a shortener cannot hide its destination from this. Stops after 10 hops, and refuses to follow a redirect into private address space. Costs $0.005 USDC per call via x402",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "examples": [
          "https://bit.ly/example"
        ],
        "description": "The URL to resolve, e.g. a shortened or tracked link."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Where does this link actually go?"
}
site_pages 1 change
{
  "name": "site_pages",
  "description": "The pages a site declares in its sitemap, with last-modified dates, located via robots.txt first and the conventional /sitemap.xml second. Use to enumerate a documentation set or a blog archive before deciding what to read, instead of crawling blindly. A sitemap index is reported as such, so you know to call again for the child sitemaps. Costs $0.008 USDC per call via x402 on Base.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "examples": [
          "https://example.com"
        ],
        "description": "Site root (e.g. 'https://example.com') or a sitemap URL directly."
      },
      "limit": {
        "type": "string",
        "examples": [
          "200"
        ],
        "description": "Maximum entries to return. Default 200, maximum 1000."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "What pages does this site publish?"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.mcpscores/url-intel"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.mcpscores/url-intel"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Furl-intel.svg)](https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Furl-intel?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Furl-intel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Furl-intel.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Furl-intel.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Furl-intel?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b5a546b60a1b98f9…, first seen 2026-10-17, included at leaf 2855 of 42,248. Version history · verify what your client received.

Tools (5)

Compare: most reliable data servers · most reliable web servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mcpscores Url Intel MCP server down right now?

As of 2026-10-21 23:33 UTC, the Mcpscores Url Intel MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Mcpscores Url Intel MCP server provide?

Mcpscores Url Intel MCP server advertises 5 tools, including demand_report, request_data, resolve_url, site_pages, url_headers.

How do I install Mcpscores Url Intel MCP server?

Point your MCP client at this streamable-http endpoint: https://url-intel.bowling-anthony.workers.dev/mcp

Is the Mcpscores Url Intel MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Mcpscores Url Intel MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve