RentCast API MCP server
io.rentcast/apirentcast.iostreamable-httpv1.0.0Scanned
Official RentCast MCP server for US property, rental, listing and real estate market data.
4 tools: 1 can delete or cancel things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RentCast API MCP server can do
The RentCast API MCP server is published by rentcast.io, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: execute-request). 3 tools only read.
2 tools bring in text other people can write (list-endpoints and execute-request).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Deletes or cancels 1Claude Code: deny
execute-requestExecutes an API request with a given HAR request object.Reads text others writeNo findings
Why it is in this group
- The name "execute-request" says "execute": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Executes an API request with a given HAR request object.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
get-endpointGets detailed information about a specific API endpoint, including security schemes and serversNo findings
Why it is in this group
- The name "get-endpoint" says "get": a word for reading.
Description, as the server wrote it Gets detailed information about a specific API endpoint, including security schemes and servers
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list-endpointsLists all API paths and their HTTP methods with summaries, organized by path.Reads text others writeNo findings
Why it is in this group
- The name "list-endpoints" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search-endpointsPerforms a deep search through paths, operations, and parameters to discover relevant API endpoints.No findings
Why it is in this group
- The name "search-endpoints" says "search": a word for reading.
Description, as the server wrote it Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http api https://developers.rentcast.io/mcpclaude mcp add --transport http api https://developers.rentcast.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__api__list-endpoints",
"mcp__api__get-endpoint",
"mcp__api__search-endpoints"
],
"ask": [],
"deny": [
"mcp__api__execute-request"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as api. Review it before you use it.
Capability tags behind 2 rules
- mcp__api__list-endpoints untrusted-input
- mcp__api__execute-request untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.rentcast/api/verify?hash=752e54238171283df5dfcbab5fdba25edd2c42dd85de618b9187838187f7046f" | jq -e '.changed == false'Pinned hash 752e54238171, from Nov 21, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.rentcast/api/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.rentcast/api)Source: MCP Registry. Synced Nov 21, 2026, 20:18 UTC.
RentCast API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RentCast API MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RentCast API MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: execute-request.
Can the RentCast API MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the RentCast API MCP server have?
- 4 tools: 1 destructive, 3 read. execute-request, list-endpoints, get-endpoint and search-endpoints.
Does the RentCast API MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RentCast API MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.