rentrollapi
Registry code: 05d774117f3f92c5
Extract verified structured data from CRE rent rolls (PDF, Excel, CSV, scans) with built-in checks
from a public catalogue that lists it, not from the operator
- endpoint
- https://rentrollapi.com/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 rentrollapi live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is rentrollapi free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rentrollapi have?
- 2 tools: extract_operating_statement, extract_rent_roll.
- Is rentrollapi 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.
90 days 99.7%· all time 99.7%
last good check
of 2 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- extract data from a rent roll
- extract a t12 operating statement
- takes → gives
- documents → data
- tools
- 2 reads
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.
through this hub
successful
what callers paid
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
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.
extract_operating_statement reads unknown 24h ago
Extract structured, verified data from a commercial real estate T12 / operating statement (trailing-twelve-month income and expense report; PDF, Excel .xlsx, or CSV; native or scanned). Returns property info, reporting months, and categorized line items (income, expenses, subtotals) with monthly values and totals, plus a deterministic verification report that reconciles row totals against monthly values and Effective Gross Income, Total Operating Expenses, and Net Operating Income against the underlying rows. Every field carries a status and confidence; uncertain fields are flagged, never silently guessed. Anonymous use is limited to 3 documents/day; pass an API key from rentrollapi.com via the X-Api-Key header for more.
{ "type": "object", "required": [ "documentBase64", "fileName" ], "properties": { "fileName": { "type": "string", "description": "Original file name including extension, e.g. 't12.pdf' — the extension guides format detection." }, "documentBase64": { "type": "string", "description": "The operating statement document encoded as base64 (PDF, XLSX, or CSV bytes). Max 25 MB decoded." } } }arguments 17 linesextract_rent_roll reads unknown 24h ago
Extract structured, verified data from a commercial real estate rent roll document (PDF, Excel .xlsx, or CSV; native or scanned). Returns property info, one record per unit (unit number, tenant, square feet, lease dates, rents, occupancy), stated totals, and a deterministic verification report that reconciles recomputed totals against the document's stated totals. Every field carries a status and confidence; uncertain fields are flagged, never silently guessed. Anonymous use is limited to 3 documents/day; pass an API key from rentrollapi.com via the X-Api-Key header for more.
{ "type": "object", "required": [ "documentBase64", "fileName" ], "properties": { "fileName": { "type": "string", "description": "Original file name including extension, e.g. 'rent-roll.pdf' — the extension guides format detection." }, "documentBase64": { "type": "string", "description": "The rent roll document encoded as base64 (PDF, XLSX, or CSV bytes). Max 25 MB decoded." } } }arguments 17 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id05d774117f3f92c5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/05d774117f3f92c5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/05d774117f3f92c5?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.