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

sukukfi

https://mcp.sukuk.fi

Registry code: fc8b97df992d1e5d

api record

Public data for SukukFi, an on-chain Islamic trade finance protocol on Berachain that funds wholesale telecom receivables. Use get_vault_stats for live on-chain figures, search_docs/get_doc for methodology and risk documentation, get_contracts for addresses, and get_vault_terms for the live Phase 1 vault terms. Yields are illustrative targets, not guarantees. This server exposes public data only.

endpoint
https://mcp.sukuk.fi/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 sukukfi live?
Yes — it answered the hub's last check (checked 53m ago). It answered 99% of checks over the last 30 days.
Is sukukfi free to use?
Yes — the hub reached it with no key and no payment.
What tools does sukukfi have?
5 tools: search_docs, get_doc, get_contracts, get_vault_stats, get_vault_terms.
Is sukukfi 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.3%

90 days 99.5%· all time 99.5%

latency
125ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 398 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
  • get on-chain vault statistics
  • read vault deposit terms
  • search protocol documentation
  • get contract addresses
takes → gives
text → data, text
tools
5 reads
_ 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
3 open 2 never probed 3 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.

  • get_contracts reads open 14h ago

    Verified SukukFi contract addresses on Berachain Mainnet with explorer links: the duPRT share token and the vault proxies for each accepted asset.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_vault_stats reads open 14h ago

    Current on-chain metrics for SukukFi vaults on Berachain: capital held, pending deposits and redemptions, and participant counts. Refreshed from Berachain RPC.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "asset": {
          "enum": [
            "USDC.e",
            "USD₮0",
            "HONEY"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • get_vault_terms reads open 14h ago

    Deposit terms for the live SukukFi vault: target yield, capacity, minimum ticket, lockup, accepted assets and settlement cycle.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • search_docs reads unknown 7h ago

    Full-text search across public SukukFi writing: the documentation (how vaults work, obligor credit assessment, Islamic finance structuring, redemptions, risk, transparency) and the blog (explainers such as "is DeFi halal", "are stablecoins halal").

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "Search terms, e.g. \"obligor default\" or \"is defi halal\""
        },
        "source": {
          "enum": [
            "docs",
            "blog"
          ],
          "type": "string",
          "description": "Restrict to one corpus"
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_doc reads unknown 7h ago

    Return a full SukukFi documentation page as markdown. Call search_docs first to find a slug, or pass a known slug such as "for-capital-providers/risk-considerations".

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Page slug, e.g. \"overview\""
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 fc8b97df992d1e5d.

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