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.

co.policyforge/mcp

REMOTE · POLICYFORGE.CO · 2 COMPONENTS · SCANNED AUG 3

Generate, audit, and maintain legal policies that match what your code actually does.

39 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 Security97
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 · policyforge.co

# add to Claude Code
claude mcp add --transport http co-policyforge-mcp https://policyforge.co/api/mcp
# ~/.codex/config.toml
[mcp_servers.co-policyforge-mcp]
url = "https://policyforge.co/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-policyforge-mcp": {
      "type": "remote",
      "url": "https://policyforge.co/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add co-policyforge-mcp --url https://policyforge.co/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-policyforge-mcp:
    url: "https://policyforge.co/api/mcp"
// mcp.json
{
  "mcpServers": {
    "co-policyforge-mcp": {
      "type": "http",
      "url": "https://policyforge.co/api/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.

  • 3 Aug 26 39

    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://policyforge.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=policyforge.co CN=YR1,O=Let's Encrypt,C=US 19 Jul 2026 17 Oct 2026 RSA 2048 SHA256-RSA 56590f3f587352a8f42ce70fc39a64e7b8a
SANs: policyforge.co
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of policyforge.co. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
policyforge.co. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer realm="PolicyForge MCP", error="invalid_token", error_description="Authorization required. Connect via OAuth, or send an API key from https://policyforge.co/api-dashboard.", resource_metadata="https://policyforge.co/.well-known/oauth-protected-resource", scope="policies:read policies:write"

Bearer realm="PolicyForge MCP", error="invalid_token", error_description="Authorization required. Connect via OAuth, or send an API key from https://policyforge.co/api-dashboard.", resource_metadata="https://policyforge.co/.well-known/oauth-protected-resource", scope="policies:read policies:write"
Header Value
strict-transport-security max-age=63072000
www-authenticate Bearer realm="PolicyForge MCP", error="invalid_token", error_description="Authorization required. Connect via OAuth, or send an API key from https://policyforge.co/api-dashboard.", resource_metadata="https://policyforge.co/.well-known/oauth-protected-resource", scope="policies:read policies:write"

Protected resource metadata

Document https://policyforge.co/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://policyforge.co/api/mcp
Authorisation server https://policyforge.co
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://policyforge.co/api/mcp Auth required 401
http (plaintext) http://policyforge.co/api/mcp HTTPS enforced 308 https://policyforge.co/api/mcp
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.