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

fiber-core

https://mcp.fiber.ai

Registry code: 19718b3ca07caf0b

api record

Fiber AI API - Discovery and execution tools.

HOW TO USE (3 steps):

endpoint
https://mcp.fiber.ai/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 fiber-core live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is fiber-core free to use?
Yes — the hub reached it with no key and no payment.
What tools does fiber-core have?
5 tools: search_endpoints, call_operation, get_endpoint_details_full, list_tag_packs, list_all_endpoints.
Is fiber-core 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%

90 days 98.7%· all time 98.8%

latency
484ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 600 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find companies matching criteria
  • discover the right api operation
  • execute a company data api call
takes → gives
text, data → data
tools
4 reads1 effect unclear
_ 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 5 tools
2 open 3 never probed 2 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.

  • list_tag_packs reads open 17h ago

    List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_all_endpoints reads open 17h ago

    List available Fiber API endpoints with optional tag/search filtering.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "tags": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "limit": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "search": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "tagPack": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 53 lines
  • search_endpoints reads unknown 17h ago

    Canonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "query": {
          "type": "string"
        },
        "tagPack": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "constraints": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "excludedTags": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "preferredTags": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 76 lines
  • call_operation unknown never probed

    Execute any Fiber API operation by operationId. IMPORTANT: - Most operations require `apiKey` in the request body. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes. Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.

    mcp-tool

    {
      "type": "object",
      "required": [
        "operationId"
      ],
      "properties": {
        "params": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "operationId": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_endpoint_details_full reads unknown 14h ago

    Get COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.

    mcp-tool

    {
      "type": "object",
      "required": [
        "operationId"
      ],
      "properties": {
        "operationId": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    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 19718b3ca07caf0b.

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