Perilpulse vs Realastat
A side-by-side look at the Perilpulse and Realastat MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
R
RealastatReal Estate · Remote HTTP/SSEReal estate deal analysis from chat: rental underwriting, buy-box matching, deal library, docs.39FairAuth: oauth 2.0Verdict: choose Perilpulse for real estate work as a local process; choose Realastat for real estate over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Perilpulse when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a local stdio subprocess transport.
- You want tools like
perilpulse_risk.
RChoose Realastat when
- You need dedicated capabilities in the Real Estate domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | R Realastat | |
|---|---|---|
| Category | Real Estate | Real Estate |
| Quality signal | 53/100 · Good | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Perilpulse | View Realastat |
Tools & capabilities
Perilpulse tools 1
perilpulse_riskMulti-peril risk scores (flood, wildfire, wind, hail, crime…) for a property address. Returns A–F grades / 0–100 scores across 25+ hazard types (flood, wildfire, earthquake, wind, hail, tornado, lightning, storm surge, crime, sinkhole, and more) — HazardHub-style property risk for insurance underwr…
Realastat tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Perilpulse
{
"mcpServers": {
"perilpulse": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-perilpulse"
]
}
}
}
Realastat
{
"mcpServers": {
"realastat": {
"command": "npx",
"args": [
"-y",
"realastat"
]
}
}
}
Frequently asked questions
Perilpulse is categorized under Real Estate and uses a local stdio subprocess. Realastat belongs to Real Estate and uses a remote HTTP/SSE transport. Pick Perilpulse for real estate work and Realastat for real estate.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Perilpulse has no declared pricing — check the project's own site. Realastat has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add perilpulse and realastat as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Perilpulse has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Realastat has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.