IPMC MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEALTH_SOURCE | No | Default apache-health reports directory | |
| HEALTH_MCP_REPO | No | Path to the HealthMCP checkout | |
| PODLINGS_MCP_REPO | No | Path to the PodlingsMCP checkout |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| configure_sourcesA | Set or inspect process-level source defaults so later IPMC tool calls can omit source override arguments. |
| current_podlings_overviewB | Return a factual overview of current Incubator podlings from podlings.xml lifecycle metadata. |
| recent_changesC | Return per-podling recent deltas the IPMC should scan, excluding unchanged or static fields. |
| significant_changesC | Return a structured factual subset of recent changes: no 12-month releases, large activity shifts, and newly visible reporting or release transitions. |
| reporting_gapsB | Return podlings with Incubator reporting compliance gaps, excluding activity analysis. |
| reporting_reliabilityB | Return objective reporting reliability patterns over time, separating one-off late reporting from repeated late or missing reporting. |
| reporting_scheduleB | Return expected Incubator reporting cadence, due-this-month status, and next expected reporting period from PodlingsMCP. |
| release_visibilityB | Return release-governance visibility concerns, including no releases and activity/release mismatches. |
| release_vote_evidenceB | Return MailMCP release vote/result thread evidence for one podling alongside IPMC release visibility signals. |
| release_artifact_evidenceB | Return ReleaseMCP artifact, sidecar, cadence, Incubator naming evidence, and optional release-page and GitHub/Docker Hub/PyPI/Maven distribution hints for one podling. |
| refresh_report_cacheB | Refresh cached ASF Incubator report data used by IPMC report-narrative tools. |
| refresh_mail_cacheC | Refresh cached general@incubator.apache.org message summaries used by IPMC mail evidence tools. |
| reporting_cohortB | Return current reporting podlings grouped into non-ranked IPMC review buckets: reporting issues, release visibility issues, recent significant changes, and no obvious concerns. |
| report_narrative_signalsB | Return report-derived narrative signals such as latest reported issues, recurring issues, low observed mentor sign-off, and release visibility mismatches. |
| cross_source_mismatchesB | Return concrete mismatches between cached report narrative and current health or release evidence. |
| stalled_podlingsB | Return podlings that match the strict low-delivery, no-release stalled definition. |
| ipmc_watchlistA | Return podlings that most need IPMC attention based on combined lifecycle and health signals. |
| graduation_readinessB | Assess whether a podling appears ready, near ready, or not yet ready for graduation. |
| podling_briefB | Return an IPMC-oriented briefing for a single podling, including status, trajectory, and attention areas. |
| mentoring_attention_neededA | Return podlings where mentoring intervention appears necessary, with urgency and likely causes. |
| community_health_summaryC | Return an IPMC-level summary of community health across podlings, including strong patterns, risks, and mentoring-capacity signals. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/justinmclean/IncubatorMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server