Is the Mcpscores Dev Package Intel MCP server down?

mcp-registry/com.mcpscores/dev-package-intel · v1.0.2

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

Is this dependency current, licensed, deprecated, or already carrying a CVE?

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

Agent-readiness: B (85/100)

What to fix (2)

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%2Fdev-package-intel/fixes

{
  "name": "package_audit",
  "description": "One call that answers whether a dependency is safe to add: latest version, licence, deprecation, advisories affecting the current version, how long since the last release, and a verdict with the specific concerns found. Prefer this over calling package_info and package_vulnerabilities separately — it is one payment instead of two and applies the judgement. A clean verdict means nothing was found in these sources, not that the package is guaranteed safe. Costs $0.01 USDC per call via x402 on Base",
  "inputSchema": {
    "type": "object",
    "required": [
      "ecosystem",
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "examples": [
          "lodash"
        ],
        "description": "Package name."
      },
      "ecosystem": {
        "type": "string",
        "examples": [
          "npm"
        ],
        "description": "One of 'npm', 'pypi', 'crates'."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Should I add this dependency?"
}

{
  "name": "package_info",
  "description": "Look up a package in npm, PyPI or crates.io: latest version, licence, whether it is deprecated or yanked, when it was last published, dependency count and repository. Use before writing a dependency line, or to check whether a pinned version is behind. Registries answer with hundreds of kilobytes; this returns only the facts that decide the question. Costs $0.005 USDC per call via x402 on Base.",
  "inputSchema": {
    "type": "object",
    "required": [
      "ecosystem",
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "examples": [
          "express"
        ],
        "description": "Package name, e.g. 'express', '@scope/pkg', 'requests', 'serde'."
      },
      "ecosystem": {
        "type": "string",
        "examples": [
          "npm"
        ],
        "description": "One of 'npm', 'pypi', 'crates' (aliases: node, python, rust)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Latest version and metadata for a package"
}

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/dev-package-intel"],"email":"[email protected]"}'

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

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~954 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• package_vulnerabilities ~238 tokens
• package_audit ~229 tokens
• package_info ~223 tokens
• request_data ~162 tokens
• demand_report ~102 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Fdev-package-intel.svg)](https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Fdev-package-intel?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Fdev-package-intel?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Fdev-package-intel.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcpscores%2Fdev-package-intel.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.mcpscores%2Fdev-package-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:ca28428c4d320575…, first seen 2026-10-17, included at leaf 14040 of 76,123. Version history · verify what your client received.

Tools (5)

• demand_report
• package_audit
• package_info
• package_vulnerabilities
• request_data

Compare: most reliable data servers · most reliable code servers · most reliable security servers

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

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

FAQ

Is the Mcpscores Dev Package Intel MCP server down right now?

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

How many tools does Mcpscores Dev Package Intel MCP server provide?

Mcpscores Dev Package Intel MCP server advertises 5 tools, including demand_report, package_audit, package_info, package_vulnerabilities, request_data.

How do I install Mcpscores Dev Package Intel MCP server?

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

Is the Mcpscores Dev Package 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 Dev Package 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.