Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Morphed is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
5
downloads a day
local
runs on your machine
457
downloads in 30d
What it does
Morphed Intelligence Platform MCP Server for governed HubSpot operations in Claude, ChatGPT, and compatible MCP clients
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user morphed-mcp '--' npx -y morphed-mcp-server
# 2 — ask your agent for something these tools do
# morphed-intelligence, get_partner_info, validate_api_key and 18 more
Morphed costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EUAll 1 server
eugeneboondock1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Morphed as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user morphed-mcp '--' npx -y morphed-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Morphed Intelligence Platform - Access your business data, generate insights, and create Magic Cards through Claude
No parameter schema on file.
Get partner account information and connected customers
No parameter schema on file.
Validate that the MCP server is sending the API key correctly to the platform
No parameter schema on file.
List all portals available to the partner, including the partner/owner portal and customer portals. Each row includes type, name, portal ID, status, and sync counts.
No parameter schema on file.
Connect a Zapier MCP Streamable HTTP server to this partner account.
No parameter schema on file.
List Zapier MCP connections for this partner, including status and tool counts.
No parameter schema on file.
Summarize partner Zapier MCP usage: connections, consented data sources, audit history, and optional sanitized snapshot samples.
No parameter schema on file.
Inspect Zapier MCP data for a specific customer portal: consent status, connection health, audit history, and optional sanitized snapshots.
No parameter schema on file.
Execute any Zapier MCP tool (Google Calendar, Gmail, Slack, etc.) connected to the partner\
No parameter schema on file.
Search partner content library (methodologies, templates, frameworks)
No parameter schema on file.
Upload new content to partner library
No parameter schema on file.
Analyze a specific customer HubSpot portal for insights and opportunities
No parameter schema on file.
Get key metrics and KPIs for a customer portal
No parameter schema on file.
List customer invitation magic links
No parameter schema on file.
Invite a new customer by generating a magic link invitation
No parameter schema on file.
Analyze performance across all customer portals in partner portfolio
No parameter schema on file.
Create a notification/task for a specific customer in their HubSpot
No parameter schema on file.
Get all available portals with their last sync timestamps (last_data_fetch_at). Returns the partner/owner portal and all customer portals with metadata including when data was last fetched from HubSpot. Use this to check which portals need data refresh.
No parameter schema on file.
Sync fresh HubSpot data for one or more customer portals. This fetches the latest data from HubSpot (companies, contacts, deals, tickets, etc.) and updates the partner\
No parameter schema on file.
Return the current version of the Morphed MCP server package (reads package.json at runtime).
No parameter schema on file.
System instructions for Morphed MCP: prefer MCP tools and fetch HubSpot context via HubSpot MCP if available.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Morphed or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.1.142 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digesta929db1475ae0d8ad7694855b52942f38a91487bcaf0454b2baae18cf14041d7
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (19 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
19 of the 19 recovered tools are registered only when false holds (http-server.mjs:628) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
No tool is registered unconditionally · 19 only when false holds (http-server.mjs:628) — typically when a key or option is configured. All 19 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_partner_info conditional | no tags | |
| validate_api_key conditional | no tags | |
| list_customer_portals conditional | no tags | |
| zapier_connect_server conditional | no tags | |
| zapier_list_connections conditional | no tags | |
| get_partner_zapier_data conditional | no tags | |
| get_customer_zapier_data conditional | no tags | |
| zapier_execute_tool conditional | no tags | |
| search_partner_content conditional | no tags | |
| upload_partner_content conditional | no tags | |
| analyze_customer_portal conditional | no tags | |
| get_customer_metrics conditional | no tags | |
| list_magic_links conditional | no tags | |
| invite_customer conditional | no tags | |
| analyze_portfolio_performance conditional | no tags | |
| create_customer_notification conditional | no tags | |
| get_partner_customer_portals conditional | untrusted-input | untrusted-input: keyword "fetch" |
| sync_partner_customer_data conditional | untrusted-input | untrusted-input: keyword "fetch" |
| get_package_version conditional | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta929db1475ae0d8a
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.142. Pin a release below and the command asks for exactly that one.
1.1.142
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Morphed can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.