_ registry / mcp streamable-http · checked 37m ago

forter-demo

https://www.forter.com

Registry code: d77690d154655d22

api record

DEMO MCP server on www.forter.com. Every tool result is synthetic - do NOT use to drive real merchant approve/decline actions. The PRODUCTION Forter MCP server lives at https://mcp.forter.com/mcp and is gated by a Forter account manager / Customer Success (CSM) under a signed MSA. To provision production access, contact https://www.forter.com/contact-us/. MCP Apps (ui:// resources) ship inline cards for fraud decisions, login-risk, and agent-trust - call resources/list / resources/templates/list to discover them.

endpoint
https://www.forter.com/mcp
protocol
streamable-http ·2025-03-26
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is forter-demo live?
Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
Is forter-demo free to use?
Yes — the hub reached it with no key and no payment.
What tools does forter-demo have?
5 tools: evaluate_signup_risk, lookup_dispute_evidence, check_agent_trust, evaluate_login_risk, get_fraud_decision.
Is forter-demo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.4%· all time 99.4%

latency
382ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 331 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
security & compliance identity & verification
used for
  • get a fraud decision for a transaction
  • score login risk
  • score signup risk
  • check an agent trust score
  • look up chargeback dispute evidence
takes → gives
data → data
tools
5 reads
note
demo or test
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • evaluate_signup_risk reads unknown never probed

    Returns a DEMO signup-risk score and recommended action for a new account.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "Client IP (optional)."
    },
    "email": {
      "type": "string",
      "description": "Signup email."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • lookup_dispute_evidence reads unknown never probed

    Returns DEMO chargeback dispute representment evidence data for a dispute id. Synthetic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "dispute_id"
  ],
  "properties": {
    "dispute_id": {
      "type": "string",
      "description": "Forter dispute id."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_agent_trust reads unknown 11h ago

    Returns a DEMO TACP (Trusted Agentic Commerce Protocol) trust score for an agent_id acting on behalf of a user. Synthetic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agent_id"
  ],
  "properties": {
    "agent_id": {
      "type": "string",
      "description": "Agent identifier (e.g. ChatGPT, Claude, custom)."
    },
    "user_email": {
      "type": "string",
      "description": "Email of the user the agent acts on behalf of (optional)."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • evaluate_login_risk reads unknown 11h ago

    Returns a DEMO login-risk score (0-100) for a user_id, optionally with IP and user-agent context. Synthetic - production scores come from the Forter REST account-protection API.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_id"
  ],
  "properties": {
    "ip": {
      "type": "string",
      "description": "Client IP (optional)."
    },
    "user_id": {
      "type": "string",
      "description": "Tenant user id."
    },
    "user_agent": {
      "type": "string",
      "description": "Client UA (optional)."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • get_fraud_decision reads unknown 11h ago

    Returns a DEMO Forter fraud decision (APPROVE / DECLINE / REVIEW) for a given transaction_id. Synthetic result - does not call into real Forter decisioning. Production decisions come from https://api.forter-secure.com (REST) or https://mcp.forter.com/mcp (MCP) - see https://www.forter.com/contact-us/.

    mcp-tool

    {
  "type": "object",
  "required": [
    "transaction_id"
  ],
  "properties": {
    "transaction_id": {
      "type": "string",
      "description": "Transaction id or order number."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d77690d154655d22.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d77690d154655d22/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d77690d154655d22/badge.svg)](https://brick.blue/agent/d77690d154655d22?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.