_ registry / mcp http-sse · checked 9h ago

com.liftmcp/company

https://mcp.liftmcp.com

Registry code: 3e03bdfff001ff6a

api record

LiftMCP's own server: company and product info, a website AI-readiness check, and site onboarding.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.liftmcp.com/
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 com.liftmcp/company live?
Yes — it answered the hub's last check (checked 9h ago). It answered 100% of checks over the last 30 days.
Is com.liftmcp/company free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does com.liftmcp/company have?
6 tools: verify_site, check_site_readiness, register_site, get_product_info, get_company_info, site_status.
Is com.liftmcp/company 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
376ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 3 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

_ what it can do 6 tools
2 open1 auth-required 3 never probed 3 of 6 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.

  • get_product_info open 9h ago

    Get information about the LiftMCP platform — what it does, how it works, and key concepts.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_company_info open 9h ago

    Get information about LiftMCP Ltd — the company behind the LiftMCP platform.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • site_status auth-required 9h ago

    The status of one Property in your LiftMCP organisation, or of all of them if no propertyId is given.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "propertyId": {
          "type": "string",
          "description": "A Property id; leave out to list all"
        }
      }
    }
    arguments 10 lines
  • verify_site unknown never probed

    Check the server card published on a site and, if it matches, verify the Property and switch on its MCP endpoint. Returns the endpoint and, on the first successful verify only, the MCP API key agents use to call it. Safe to repeat.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "propertyId"
      ],
      "properties": {
        "propertyId": {
          "type": "string",
          "description": "The Property id from register_site"
        }
      }
    }
    arguments 13 lines
  • check_site_readiness unknown never probed

    Check how ready a website is for AI agent interaction. Returns an AI readiness score and breakdown.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "format": "uri",
          "description": "The website URL to check (e.g. https://example.com)"
        }
      }
    }
    arguments 14 lines
  • register_site unknown never probed

    Add a website to your LiftMCP organisation as a Property and get the server card to publish on it. Needs your organisation API key in the Authorization header. Safe to repeat: a site already added is found, not added twice. Next: publish the card exactly as given at the address given, then call verify_site.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "The site, e.g. example.com or https://www.example.com"
        }
      }
    }
    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 3e03bdfff001ff6a.

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

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.