nyc-property-intel (ccedacero/nyc-property-intel) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 19 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

nyc-property-intel

MCP server giving Claude AI access to 20+ NYC public-record datasets across 9 city agencies via 18 tools — NYC property due diligence in plain English: violations, liens, sales, ownership, permits, rent stabilization, and more.

→ ccedacero/nyc-property-intel· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ccedacero

Source: Glama · also listed on github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored hereGitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SOCRATA_APP_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
2 files are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 3 credentials: SOCRATA_APP_TOKEN, RESEND_API_KEY, ANON_IP_HASH_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configMCP_TRANSPORT
configMCP_ALLOWED_HOSTS
🔐 secretSOCRATA_APP_TOKEN
configALERT_FROM_EMAIL
configALERT_EMAIL_TO
🔐 secretRESEND_API_KEY
configBACKFILL_DATASETS
configBACKFILL_RESET
configSYNC_TIER
configSYNC_SKIP_CLEANUP
🔐 secretANON_IP_HASH_SECRET
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deployDATABASE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

19/19 tools missing one or more hints — my_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyze_property (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_311_complaints (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Readable source code

2 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

1 secret sent to a request target we could not resolve (SOCRATA_APP_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/ccedacero/nyc-property-intel?variant=verified)](https://m8ven.ai/mcp/ccedacero/nyc-property-intel)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0cfdb9d418566fda1495aa366781449e73c548c1
code hash: 1a3a10c8036a95f3bf2536b0458bca703968caf65f4cf0b48196105713744a2c
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client