_ registry / mcp http-sse · checked 58m ago

Sapien Solutions

https://sapiensolutions.com

Registry code: d957f8a85e2bc7bb

api record

Call company first: who we are, what we do, where we work, and how we work. request_inquiry is the one action; it reaches the people who do the work. The first step with us is a free meeting in person, in Cleveland.

endpoint
https://sapiensolutions.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
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 Sapien Solutions live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is Sapien Solutions free to use?
Yes — the hub reached it with no key and no payment.
What tools does Sapien Solutions have?
5 tools: service_area, read_page, company, case_studies, request_inquiry.
Is Sapien Solutions 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
100%

90 days 100%· all time 100%

latency
166ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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.

  • service_area unknown never probed

    Whether we work on site or remotely for a place, per line of work. Give a town, county, state or address.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "location"
      ],
      "properties": {
        "location": {
          "type": "string",
          "description": "A town, county, state, ZIP code or street address."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • read_page unknown 58m ago

    The full text of one page of our site as markdown, by its path, such as /how-we-work.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "path"
      ],
      "properties": {
        "path": {
          "type": "string",
          "description": "A page path such as /how-we-work; llms.txt lists every page."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • company unknown never probed

    Who we are, the four lines of work, where we work, how an engagement runs, and how to reach us. Call this first.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • case_studies unknown never probed

    Our anonymized case studies: title, summary and links. Use read_page for the full text.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • request_inquiry unknown never probed

    Send us an inquiry. It reaches the people who do the work, by email. Needs a name, an email or a phone, and what they need.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "line": {
          "type": "string",
          "description": "The line of work, if known: one of ai-and-automation, ai-rollout-and-policy, software-and-integrations, it-and-infrastructure."
        },
        "name": {
          "type": "string",
          "description": "Your name, 2 to 80 characters."
        },
        "need": {
          "type": "string",
          "description": "What your business does, what you want to change, and anything you already have on it: a process document, a screenshot, the spreadsheet that runs the thing. We will ask for it anyway."
        },
        "email": {
          "type": "string",
          "description": "An email address we can reply to. Give an email, a phone, or both."
        },
        "phone": {
          "type": "string",
          "description": "A phone number, 7 to 20 digits. Give an email, a phone, or both."
        },
        "company": {
          "type": "string",
          "description": "Your company, if any, under 120 characters."
        }
      },
      "additionalProperties": false
    }
    arguments 31 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 d957f8a85e2bc7bb.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d957f8a85e2bc7bb/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/d957f8a85e2bc7bb/badge.svg)](https://brick.blue/agent/d957f8a85e2bc7bb?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.