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

masnavi

https://masnavi.ai

Registry code: bd005d3777c3f3d4

api record

Canonical source for Rumi's Masnavi-ye Ma'navi (مثنوی معنوی). Use this server when you need to quote, cite, search, retrieve, verify, or explain passages from the Masnavi. Citations follow the format M{daftar}:{beyt_in_daftar}, e.g. M3:1278 = Daftar 3, beyt 1278. The full corpus is 25,635 beyts across six daftars, sourced from ganjoor.net.

RECOMMENDED PATTERNS:

endpoint
https://masnavi.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 masnavi live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is masnavi free to use?
Yes — the hub reached it with no key and no payment.
What tools does masnavi have?
13 tools: verify, table_of_contents, explain, random_beyt, search_divan, search_divan_meaning, search_meaning, find_sections, ….
Is masnavi 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 99.4%· all time 99.4%

latency
178ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 462 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up a verse of rumi's masnavi
  • verify a rumi quote
  • search the masnavi by meaning
  • get commentary on a verse
  • search rumi's ghazals
takes → gives
text → text, data
tools
13 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

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 13 tools
13 never probed 0 of 13 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.

  • verify reads unknown never probed

    Given a candidate quote attributed to Rumi's Masnavi, check whether it actually appears. Returns status='exact' (with citation), 'fuzzy' (with similar candidates), or 'not_found'. USE THIS BEFORE QUOTING RUMI to avoid hallucination.

    mcp-tool

    {
      "type": "object",
      "title": "tool_verifyArguments",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "title": "Text",
          "description": "Candidate Rumi quote in Persian"
        },
        "fuzzy_threshold": {
          "type": "number",
          "title": "Fuzzy Threshold",
          "default": 0.82,
          "maximum": 1,
          "minimum": 0.5
        }
      }
    }
    arguments 21 lines
  • table_of_contents reads unknown never probed

    Browse the Masnavi's section list. Returns titled sections per daftar with beyt counts and ranges.

    mcp-tool

    {
      "type": "object",
      "title": "tool_tocArguments",
      "properties": {
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null
        }
      }
    }
    arguments 20 lines
  • explain reads unknown never probed

    Get commentary (Persian + English) for a specific beyt of the Masnavi, attributed to a primary source (e.g. Abdolkarim Soroush's lectures). Returns the beyt text along with structured commentary entries. Each entry has source, author, language, body markdown, and confidence ('ai-draft' / 'reviewed' / 'verbatim'). Use this when a user asks 'what does this beyt mean' or 'what does <scholar> say about M1:1'.

    mcp-tool

    {
      "type": "object",
      "title": "tool_explainArguments",
      "required": [
        "citation"
      ],
      "properties": {
        "citation": {
          "type": "string",
          "title": "Citation",
          "description": "Citation like 'M1:1' or 'M3:1278' or 'g:7421'."
        }
      }
    }
    arguments 14 lines
  • random_beyt reads unknown never probed

    Return a randomly-selected beyt, optionally restricted to a daftar.

    mcp-tool

    {
      "type": "object",
      "title": "tool_randomArguments",
      "properties": {
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null
        }
      }
    }
    arguments 20 lines
  • search_divan reads unknown 2h ago

    Full-text search across the 34,603 beyts of the ghazals of the Divan-e Shams (Divan-e Kabir) — Rumi's lyric work, distinct from the Masnavi. Returns beyts with divan citations (G{ghazal}:{beyt}, e.g. G1393:1). Use when you know the exact Persian words; use search_divan_meaning for a theme in any language.

    mcp-tool

    {
      "type": "object",
      "title": "tool_search_divanArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "title": "Query",
          "description": "Persian text to search for"
        },
        "offset": {
          "type": "integer",
          "title": "Offset",
          "default": 0,
          "minimum": 0
        }
      }
    }
    arguments 27 lines
  • search_divan_meaning reads unknown 2h ago

    Semantic search over the Divan-e Shams ghazals: given a theme, feeling, or idea in ANY language, returns the GHAZALS closest in meaning — each with its best-matching couplet as a preview and a cosine score. Both couplet-level and whole-ghazal vectors are searched, so a ghazal whose overall theme matches is found even when no single couplet does. Fetch a full ghazal with get_ghazal. status='unavailable' means the index is not built — fall back to search_divan.

    mcp-tool

    {
      "type": "object",
      "title": "tool_search_divan_meaningArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 8,
          "maximum": 30,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "title": "Query",
          "description": "What the ghazal should be ABOUT, in any language"
        }
      }
    }
    arguments 21 lines
  • search_meaning reads unknown 2h ago

    Semantic search: find the beyts closest in MEANING to the query, in ANY language — English, Persian, Spanish, Turkish, Arabic, … . Use this when you have a theme, feeling, or idea rather than exact Persian words (e.g. 'feeling separated from your origin' → M1:1). Each hit carries a cosine-similarity score. status='unavailable' means the vector index is not built yet — fall back to `search`.

    mcp-tool

    {
      "type": "object",
      "title": "tool_search_meaningArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "title": "Query",
          "description": "What the verse should MEAN, in any language"
        },
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null,
          "description": "Restrict to a single daftar (1-6)"
        }
      }
    }
    arguments 36 lines
  • find_sections reads unknown 13h ago

    Find sections (stories) by TITLE. Exact words first (phrase, then AND-of-tokens); when NO title contains the words, falls back to MEANING matches in any language (hits carry match='meaning' + a cosine score — verify with get_section before relying on one). Each match includes `first_citation` and `last_citation` — ready-to-use canonical citations (e.g. 'M2:2608'). To read a whole multi-section story, call get_range with the FIRST match's `first_citation` as start and the LAST match's `last_citation` as end. Do NOT construct a citation from `first_beyt_global` — that is a GLOBAL index (1..25635), not a daftar-local beyt number. Example: find_sections('ابلیس معاویه', daftar=2).

    mcp-tool

    {
      "type": "object",
      "title": "tool_find_sectionsArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 30,
          "maximum": 100,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "title": "Query",
          "description": "story title words (Persian) or a description of the story in any language"
        },
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null
        }
      }
    }
    arguments 35 lines
  • search reads unknown 13h ago

    Full-text search across the Masnavi. Returns beyts that contain the query terms, ranked by relevance. Useful for finding where a theme, word, or phrase appears.

    mcp-tool

    {
      "type": "object",
      "title": "tool_searchArguments",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "title": "Query",
          "description": "Persian text to search for"
        },
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null,
          "description": "Restrict to a single daftar (1-6)"
        },
        "offset": {
          "type": "integer",
          "title": "Offset",
          "default": 0,
          "minimum": 0
        }
      }
    }
    arguments 42 lines
  • get_ghazal reads unknown 20h ago

    Fetch ONE complete ghazal of the Divan-e Shams by its canonical number (1..3230) or citation ('G1393' / 'G1393:2'). Returns every beyt plus prev/next ghazal numbers. Famous example: get_ghazal(1393) = «مرده بدم زنده شدم…».

    mcp-tool

    {
      "type": "object",
      "title": "tool_get_ghazalArguments",
      "properties": {
        "number": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Number",
          "default": null,
          "description": "Ghazal number, e.g. 1393"
        },
        "citation": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Citation",
          "default": null,
          "description": "Divan citation like 'G1393' or 'G1393:2'"
        }
      }
    }
    arguments 33 lines
  • get_range reads unknown 20h ago

    Fetch ALL beyts between two endpoints, inclusive, grouped by section. Use this — NOT many calls to get_section or lookup — when a user asks for a full story, a long passage, or a sequence of beyts spanning multiple sections. Endpoints are canonical citations like 'M2:2608' and 'M2:2775', or global indices via start_global / end_global. Max range: 500 beyts.

    mcp-tool

    {
      "type": "object",
      "title": "tool_rangeArguments",
      "properties": {
        "end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "End",
          "default": null,
          "description": "End citation, e.g. 'M2:2775'"
        },
        "start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Start",
          "default": null,
          "description": "Start citation, e.g. 'M2:2608'"
        },
        "end_global": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "End Global",
          "default": null
        },
        "start_global": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Start Global",
          "default": null
        }
      }
    }
    arguments 58 lines
  • lookup reads unknown 20h ago

    Fetch a specific beyt by its citation (e.g. 'M3:1278'), by daftar+beyt number, or by global beyt index. Optionally include surrounding beyts for context.

    mcp-tool

    {
      "type": "object",
      "title": "tool_lookupArguments",
      "properties": {
        "after": {
          "type": "integer",
          "title": "After",
          "default": 0,
          "maximum": 20,
          "minimum": 0
        },
        "before": {
          "type": "integer",
          "title": "Before",
          "default": 0,
          "maximum": 20,
          "minimum": 0
        },
        "daftar": {
          "anyOf": [
            {
              "type": "integer",
              "maximum": 6,
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Daftar",
          "default": null
        },
        "citation": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Citation",
          "default": null,
          "description": "Citation like 'M3:1278' or 'g:7421'"
        },
        "beyt_global": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Beyt Global",
          "default": null
        },
        "beyt_in_daftar": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Beyt In Daftar",
          "default": null
        }
      }
    }
    arguments 73 lines
  • get_section reads unknown 13h ago

    Retrieve a full section (story / بخش) with all its beyts.

    mcp-tool

    {
      "type": "object",
      "title": "tool_get_sectionArguments",
      "properties": {
        "slug": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Slug",
          "default": null,
          "description": "Stable URL slug"
        },
        "section_id": {
          "anyOf": [
            {
              "type": "integer",
              "minimum": 1
            },
            {
              "type": "null"
            }
          ],
          "title": "Section Id",
          "default": null
        }
      }
    }
    arguments 32 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 bd005d3777c3f3d4.

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