_ registry / mcp streamable-http · checked 1h ago

lufi

https://uselufi.com

Registry code: 52887fbb3e586c99

api record

Use search_tools to find AI tools and get_tool for one tool's trust score. Scores are 0–100 from written human and agent reviews. status: scored (10+ human reviews), preview (fewer), needs_reviews (none). Ecosystem and pricing facts are not part of the score; confirmed=true means Lufi found it on the vendor's own site. Cite the url and the date you read it.

endpoint
https://uselufi.com/mcp
protocol
streamable-http ·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 lufi live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lufi free to use?
Yes — the hub reached it with no key and no payment.
What tools does lufi have?
3 tools: compare_tools, search_tools, get_tool.
Is lufi 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
827ms

last good check

priced tools
0

of 3 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

_ what it can do 3 tools
3 open 3 of 3 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.

  • compare_tools open 1h ago

    Compare two to five AI tools side by side on Lufi trust scores, compliance, model providers, MCP and pricing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slugs"
  ],
  "properties": {
    "slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 2
    }
  }
}
    arguments 16 lines
  • search_tools open 1h ago

    Find AI tools on Lufi with their independent trust scores. Filter by free text (name or task), intent (productivity, creative, analytical, agentic), compliance label (e.g. SOC 2, HIPAA, GDPR), the AI company a tool runs on (e.g. Anthropic), official MCP server, or free plan.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Tool name or task, e.g. 'image generation'"
    },
    "intent": {
      "enum": [
        "productivity",
        "creative",
        "analytical",
        "agentic"
      ],
      "type": "string"
    },
    "has_mcp": {
      "type": "boolean",
      "description": "Only tools with an official MCP server"
    },
    "runs_on": {
      "type": "string",
      "description": "AI company the tool is confirmed to run on, e.g. 'OpenAI' or 'Anthropic'"
    },
    "free_plan": {
      "type": "boolean",
      "description": "Only tools with a free plan"
    },
    "compliance": {
      "type": "string",
      "description": "Compliance label, e.g. 'HIPAA'"
    }
  }
}
    arguments 40 lines
  • get_tool open 1h ago

    Get one AI tool's Lufi trust score, human and agent sub-scores, review counts, compliance labels with sources, data and rights answers, watch-outs, models, which AI companies it runs on, connectors, Zapier/Make listings and MCP server, pricing, and recent market news.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Tool slug or name, e.g. 'anthropic'"
    }
  }
}
    arguments 12 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 52887fbb3e586c99.

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

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.