MakerPortal MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to MakerPortal deterministic engineering and model-memory solvers: Do solver assumptions and uncertainty stay visible when numerical methods and hardware catalogs change?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Deterministic engineering solvers for biquad design, room acoustics and LLM VRAM-fit calculations.

What we know

Thin transport shim to MakerPortal's deterministic solver API. The package intentionally contains no solver logic; it forwards tool calls to makerportal.ai so MCP and published web answers share the same computation path and provenance URLs.

Maintenance / activity evidence

@makerportal/mcp 0.1.1 published 2026-09-04T20:42:39.910Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read/compute only; no external system mutation.
Optional bearer license key.
Sensitive access: Engineering design inputs may be proprietary

Low operational authority; engineering decisions still require domain validation.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do solver assumptions and uncertainty stay visible when numerical methods and hardware catalogs change?

The bounded review of the publisher's documented MakerPortal deterministic engineering and model-memory solvers and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Low operational authority; engineering decisions still require domain validation.
Read/compute only; no external system mutation.
Optional bearer license key.
Inputs are sent to makerportal.ai; service returns deterministic computed outputs and provenance.
Sensitive access: Engineering design inputs may be proprietary
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Package is a bridge, not an offline solver.
Answers are licensed free-with-attribution and include a canonical provenance URL.
Remote host is part of the trust boundary.
Only the documented solver families are supported.

Original activity observations

@makerportal/mcp 0.1.1 published 2026-09-04T20:42:39.910Z

Technical identity

npm/@makerportal/mcp

Exact implementation source: https://www.npmjs.com/package/@makerportal/mcp ↗
Reviewed resource type: MCP Server
Repository identity: makerportal/mcp
Package identity: npm:@makerportal/mcp
Service endpoint: https://makerportal.ai/api/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@makerportal/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher also offers remote HTTP https://makerportal.ai/api/mcp.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add makerportal -- npx -y @makerportal/mcp
Configure / authenticate
MCP100 setup guide
Choose local Claude Code npx registration or remote https://makerportal.ai/api/mcp. Do not pass local stdio JSON in a remote-only client.
Check connection
Suggested check
After `claude mcp add makerportal -- npx -y @makerportal/mcp`, inspect the deterministic engineering solver tools; avoid external side effects.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `makerportal`, run `claude mcp remove makerportal` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: No vendor API key required by publisher server; not applicable.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove makerportal

Official Documentation & Sources

What it does

Thin transport shim to MakerPortal's deterministic solver API. The package intentionally contains no solver logic; it forwards tool calls to makerportal.ai so MCP and published web answers share the same computation path and provenance URLs.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Deterministic engineering solvers for biquad design, room acoustics and LLM VRAM-fit calculations.

Representative uses

Design/check digital biquad filters
Analyze rectangular-room modes and Schroeder/Bolt-area metrics
Estimate LLM VRAM fit/KV cache/context/throughput limits

Limitations

Package is a bridge, not an offline solver.
Answers are licensed free-with-attribution and include a canonical provenance URL.
Remote host is part of the trust boundary.
Only the documented solver families are supported.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional bearer license key.
Permissions: Read/compute only; no external system mutation.
Data handling: Inputs are sent to makerportal.ai; service returns deterministic computed outputs and provenance.
Cost: freemium
Risk and cautions: Low operational authority; engineering decisions still require domain validation.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Engineering design inputs may be proprietary
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Design/check digital biquad filters; Analyze rectangular-room modes and Schroeder/Bolt-area metrics; Estimate LLM VRAM fit/KV cache/context/throughput limits.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @makerportal/mcp. Recorded endpoint: https://makerportal.ai/api/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: MAKERPORTAL_LICENSE_KEY (optional); MAKERPORTAL_API_URL (optional). No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Keyless free tier by default; optional license key raises/changes entitlement. A demo or keyless description is not independently verified read-only authority. Check the documented tool permissions rather than inferring authority from that label.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read/compute only; no external system mutation.

What data-handling boundary should I consider?

Inputs are sent to makerportal.ai; service returns deterministic computed outputs and provenance. Recorded sensitive-access context: Engineering design inputs may be proprietary.

What limitations and risks should I check before use?

Low operational authority; engineering decisions still require domain validation. Package is a bridge, not an offline solver. Answers are licensed free-with-attribution and include a canonical provenance URL. Remote host is part of the trust boundary. Only the documented solver families are supported. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.