catalog-api-mcp-server

MCP (Model Context Protocol) server “pilot” used from VS Code to validate or manage the state of P&C, exposing locally configured MCP tools (as defined in the referenced Java service).

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ Infrastructure mcp tooling local-dev catalog spring-ai java

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

100

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Security posture is largely unknown from the provided README. Because the server is described as a local jar started from VS Code, TLS/auth/scopes/rate limiting are not documented. Validate that tool execution does not expose sensitive catalog data without access controls, and ensure secrets (if any) are handled via environment variables/config rather than logs.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want to experiment with MCP tool calling locally (e.g., with Spring AI tools integration) and you control the runtime environment.

Avoid When

You need strong network-based security, documented operational guarantees, or clearly specified idempotent/retry semantics.

Use Cases

• Local/interactive tool use via VS Code MCP integration to query or validate catalog status/state
• Development/testing of P&C state management logic through MCP tools
• Integrating catalog status functions into an AI agent workflow running locally

Not For

• Production multi-tenant deployments without security hardening
• Use as a public API gateway without explicit access controls
• Environments where installing/running a local Java jar is not acceptable

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: None documented in provided README (assumed local execution)

OAuth: No Scopes: No

The README describes starting a local MCP server via a Java jar and does not document authentication/authorization mechanisms for the MCP endpoints/tools.

Pricing

Free tier: No

Requires CC: No

No pricing information provided; appears to be a self-hosted/open-source-style component.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ README shows only VS Code MCP client configuration; tool names/inputs/outputs and error semantics are not included in the provided text.
⚠ Tool contracts are referenced indirectly via a Java file link; an agent may not know exact parameters without deeper docs/source.
⚠ The setup uses a locally built jar path; version mismatch (jar filename/snapshot) could cause startup failures.

Alternatives

Direct REST/GraphQL API (if available) instead of MCP for agent calls Using a dedicated catalog/status service with an OpenAPI-described REST interface Implementing an MCP server with fully documented tools/contracts and robust auth/error semantics

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for catalog-api-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.