IPMC MCP

A small MCP server for Apache Incubator PMC oversight views.

It composes:

podling lifecycle data from apache-podlings-mcp
community and report signals from apache-health-mcp
cached Incubator report entries from apache-incubator-reports-mcp
Incubator general-list messages from apache-incubator-mail-mcp, searched live per podling with the cache as fallback
live Incubator release vote/result thread evidence from apache-incubator-mail-mcp
release artifact, signature, checksum, cadence, release download page, and optional platform-distribution evidence from apache-incubator-releases-mcp
ASF naming, project-website branding, and third-party trademark use checks from apache-trademark-mcp

It exposes opinionated Incubator-level tools to help the IPMC:

identify podlings needing attention
scan recent podling-level changes
find Incubator reporting gaps
surface recurring or unresolved report-narrative issues from cached Incubator reports
highlight concrete mismatches between report narrative and current health or release evidence
review release visibility and Incubator release vote evidence through a governance lens
identify tightly-defined stalled podlings
assess graduation readiness
generate podling briefings
flag mentoring intervention needs
summarize community-health patterns across podlings

Requirements

Python 3.12+

Install

python3 -m pip install .

For development tools:

python3 -m pip install -e .[dev]

Run

After installation, run the stdio MCP server with:

ipmc-mcp \
  --health-source /path/to/incubator/tools/health/reports \
  --report-source /path/to/ReportMCP/.cache/incubator-reports \
  --mail-source /path/to/MailMCP/.cache/incubator-general-mail

For local development without installing first, you can still run:

PYTHONPATH=/path/to/HealthMCP/src:/path/to/PodlingsMCP/src:/path/to/ReportMCP/src:/path/to/MailMCP/src:/path/to/ReleaseMCP/src \
  python3 server.py \
  --health-source /path/to/incubator/tools/health/reports \
  --report-source /path/to/ReportMCP/.cache/incubator-reports \
  --mail-source /path/to/MailMCP/.cache/incubator-general-mail

By default the server uses stdio, so it is intended to be launched by an MCP client.

To serve the same JSON-RPC/MCP protocol over HTTP instead, pass --http:

ipmc-mcp \
  --http \
  --host 127.0.0.1 \
  --port 8080 \
  --health-source /path/to/incubator/tools/health/reports \
  --report-source /path/to/ReportMCP/.cache/incubator-reports \
  --mail-source /path/to/MailMCP/.cache/incubator-general-mail

HTTP mode uses the official MCP Streamable HTTP transport at /mcp and exposes a simple GET /health endpoint. --host and --port only affect HTTP mode. For public hosting and Claude connector setup, see docs/hosting.md.

Example MCP client config

{
  "mcpServers": {
    "ipmc": {
      "command": "ipmc-mcp",
      "args": [
        "--health-source",
        "/path/to/incubator/tools/health/reports",
        "--report-source",
        "/path/to/ReportMCP/.cache/incubator-reports",
        "--mail-source",
        "/path/to/MailMCP/.cache/incubator-general-mail"
      ]
    }
  }
}

The default runtime imports its source MCP libraries from installed packages:

apache-podlings-mcp
apache-health-mcp
apache-incubator-reports-mcp
apache-incubator-mail-mcp
apache-incubator-releases-mcp

When installed with pip, these dependencies are pulled from their Git repositories. If you run server.py directly from a checkout instead, make the source packages importable with PYTHONPATH or install them first.

Configure startup defaults with command-line arguments or environment variables:

--podlings-source or IPMC_PODLINGS_SOURCE: optional URL or local path for podlings.xml
--health-source or IPMC_HEALTH_SOURCE: local path for apache-health report Markdown files
--report-source or IPMC_REPORT_SOURCE: local path for ReportMCP cached ASF Incubator report files
--mail-source or IPMC_MAIL_SOURCE: local path for MailMCP cached ASF Incubator general-list message files
--mail-api-base or IPMC_MAIL_API_BASE: MailMCP/Pony Mail API base URL for live Incubator general-list search

General-list mail is fetched live for every podling a tool call is about, so the evidence is as recent as the list. The --mail-source cache is a fallback for podlings whose live search fails and a store for the live results; cached messages older than the live window are kept alongside them. The mail metadata reports mode (live, live+cache, cache or unavailable), source_by_podling and live_failures so a reader can see which podlings came from where.

--release-dist-base or IPMC_RELEASE_DIST_BASE: optional ReleaseMCP current release base URL or local release directory; when unset, ReleaseMCP discovers the podling download page
--release-archive-base or IPMC_RELEASE_ARCHIVE_BASE: ReleaseMCP archive.apache.org base URL or local archive directory
--http: serve JSON-RPC/MCP over HTTP instead of stdio
--host: HTTP bind host when --http is set; defaults to 127.0.0.1
--port: HTTP bind port when --http is set; defaults to 8080

Source defaults can also be set once per MCP session with configure_sources. Normal tool calls should only pass task arguments such as podling, limit, or filters; per-tool source arguments are for one-off overrides.

Test

python3 -m unittest discover -s tests -v

Coverage

python3 -m coverage run -m unittest discover -s tests
python3 -m coverage report -m

Coverage is scoped to the local ipmc package so imported source MCP libraries do not dilute the report.

Architecture

See docs/architecture.md for the module layout, runtime flow, and testing structure.

Usage Examples

These examples show prompts an IPMC member or mentor could type into an MCP client.

Monthly IPMC Review Workflow

Use this when preparing for a monthly Incubator oversight pass:

"What changed across current podlings since the last IPMC review?"
"Which podlings need IPMC attention this month, and why?"
"Which podlings have crossed a year without a visible release, or show a meaningful activity shift?"
"Group this reporting cohort into reporting issues, release visibility issues, recent changes, and no obvious concerns."
"Show me current podlings with reporting gaps, but keep that separate from community health concerns."
"Which podlings have repeated reporting reliability issues rather than a one-off late report?"
"Which current podlings call out unresolved issues in their recent Incubator reports?"
"Show me recurring issues from cached Incubator reports, and flag where the latest report still needs mentor follow-up."
"Compare reported podling issues with health signals and tell me which podlings need follow-up."
"Show me podlings where the latest report narrative and current health evidence point in different directions."
"Which current podlings do not appear to have a recent Incubator report?"
"Highlight podlings where the report narrative and recent health metrics point to different risks."
"Which podlings have release visibility concerns that the IPMC should look at?"
"Which podlings look genuinely stalled, based on low activity, low discussion, and no recent releases?"
"Give me a detailed brief for the podlings that look most concerning."

This gives reviewers a short queue of what changed, what needs attention, and what evidence supports each opinion.

Mentor Checking Their Podlings

Use this when a mentor wants a fast status check before following up with podling communities:

"Give me a focused brief for FooPodling covering reporting, releases, mentoring, and community health."
"What is FooPodling's current Incubator reporting schedule?"
"Does FooPodling look ready for graduation, and what evidence is missing?"
"Show the recent Incubator report evidence for FooPodling, including issues, last release, and observed mentor sign-offs."
"For FooPodling, separate source facts from IPMC interpretation and tell me what I should verify with the community."
"What has FooPodling reported as unfinished issues, and do the health metrics support those concerns?"
"Show me FooPodling's mentor sign-off evidence without treating partial sign-off as a failure."
"Which podlings appear to need mentor intervention?"
"Show me podlings with missing mentor sign-offs or weak mentor coverage."

This keeps source facts, derived concerns, and confidence visible so mentors can decide what needs action versus clarification.

General List Mail Evidence

Use this when a reviewer wants to check Incubator general-list discussion alongside podling reports and health signals:

"Search general incubator mail for recent FooPodling graduation, release, or retirement discussion and summarize the relevant email evidence."
"For FooPodling, compare Incubator report concerns with recent general-list email threads that mention the podling."
"Show likely Incubator release vote and result threads for FooPodling and compare them with release visibility signals."
"Show FooPodling release artifacts, signatures, checksums, and Incubator naming evidence."

Generating a Board Summary

This server is not a board tool, but it can help assemble Incubator context for a human-written board report:

"Summarize the main community-health themes across current podlings, with examples."
"Which high-risk podlings may need narrative attention in the Incubator report?"
"Use recent Incubator reports to identify repeated podling themes that may need IPMC follow-up."
"Find podlings whose report narratives mention graduation blockers and summarize the supporting health evidence."
"Which podlings have recurring issues across their Incubator report history?"
"Give me an evidence-backed list of podlings where the report narrative and release visibility both need attention."
"List reporting compliance issues separately from release-governance concerns."
"Give me short evidence-backed briefs for the podlings most likely to be mentioned by name."

The intended output is briefing material for IPMC judgment, not text that should be copied into a board report without review.

Tools

Set source paths once with configure_sources. After that, use the normal tool arguments below; only pass source paths to an individual tool when you really want to override the session defaults for that one call.

`configure_sources`

Set or inspect the source paths used by later tool calls.

`current_podlings_overview`

Return a factual overview of current Incubator podlings from podlings.xml lifecycle metadata, similar to the current-projects table on the Incubator website.

Arguments:

podlings_source: optional podlings.xml source override
as_of_date: optional YYYY-MM-DD date for incubation duration
limit: optional max number of results
include_descriptions: optional boolean, defaults to true

`recent_changes`

Return per-podling recent deltas the IPMC should scan. This is delta-based only: unchanged/static fields are excluded.

Arguments:

as_of_date: optional YYYY-MM-DD date for duration-sensitive views
podling: optional podling name filter
limit: optional max number of results

`significant_changes`

Return a structured factual subset of recent changes that usually merit IPMC scan attention. This currently includes podlings with no visible releases in the 12-month health window, review-worthy activity shifts between the 3-month and 12-month windows, newly missing reports, and release visibility disappearing.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results
include_signals: optional signal filter list

`reporting_gaps`

Return podlings with Incubator reporting compliance gaps. Activity signals are intentionally excluded.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results
include_gaps: optional gap filter list

`reporting_reliability`

Return objective reporting reliability patterns over time, grouped into consistently on time, occasional late, repeated late, repeated missing, and reporting data unavailable. Categories compare observed report counts with the expected Incubator cadence: monthly for the first quarter, then quarterly after that. A single missed expected report is treated as an occasional catch-up-next-month case, not a systemic issue. Exact due-date timeliness is not visible from rolling report counts.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results per category
include_categories: optional reporting reliability category filter list

`reporting_schedule`

Return expected Incubator reporting cadence, due-this-month status, and next expected reporting period from PodlingsMCP.

Arguments:

as_of_date
report_month: optional reporting month in YYYY-MM format
podling: optional podling name filter
due_this_month: optional boolean filter
limit: optional max number of results

`release_visibility`

Return release-governance visibility concerns, including no releases in 12 months, release gaps of at least 6 months, and activity-without-release mismatches.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results
include_signals: optional release visibility signal filter list

`release_vote_evidence`

Return likely MailMCP release vote/result thread evidence for one podling alongside IPMC release visibility signals.

Arguments:

podling: required podling name
as_of_date
mail_timespan: optional MailMCP timespan expression, defaults to the MailMCP release-search window
limit: optional max number of vote/result threads

`release_artifact_evidence`

Return ReleaseMCP artifact, signature, checksum, cadence, Incubator naming evidence, optional release download page checks, and optional GitHub, Docker Hub, PyPI, and Maven distribution hints for one podling.

Arguments:

podling: required podling name
release_dist_base: optional current release base URL or local release directory; when omitted, ReleaseMCP discovers the podling download page
release_max_depth: optional traversal depth under the podling directory, 0 to 2; defaults to 2, which reaches release trees laid out as <version>/<subproject>/<file>; use 0 or 1 for a shallower scan
release_page_url: optional Apache project release download page URL or local HTML file to inspect; use auto to let ReleaseMCP discover the page
include_platforms: optional boolean; when true, asks ReleaseMCP to include GitHub, Docker Hub, PyPI, and Maven distribution hints
github_project: optional apache/ GitHub repository name; defaults to the podling slug in ReleaseMCP
docker_images: optional Docker Hub image names in namespace/repository form
pypi_packages: optional PyPI package names; defaults to apache- in ReleaseMCP
maven_group_ids: optional Maven groupIds; defaults to org.apache. in ReleaseMCP

When platform checks are not requested, the platform_distribution_checks response field is an explicit not-requested status rather than null. When release page checks are not requested, the release_page_checks response field is also an explicit not-requested status. Pass release_page_url: "auto" to request ReleaseMCP release download page discovery and checks without supplying the page URL. release_source.source_statuses gives each listing source's file count and, when a directory could not be read, an error saying the release list may be incomplete.

`refresh_report_cache`

Refresh cached ASF Incubator report data used by the report-narrative and cross-source tools.

Arguments:

report_source: optional cache directory override
years: optional years of history to cache
full_history: optional boolean to cache full history instead of recent reports
limit: optional max number of reports to cache
report_url: optional single report URL to cache instead of refreshing recent reports
report_id: optional report id for a single report URL

`refresh_mail_cache`

Refresh cached general@incubator.apache.org message summaries used by mail evidence tools.

Arguments:

mail_source: optional cache directory override
mail_api_base: optional Pony Mail API base URL
mail_timespan: optional MailMCP timespan expression
query: optional search query
limit: optional max number of message summaries to cache

`reporting_cohort`

Return current reporting podlings grouped into non-ranked IPMC review buckets: reporting issues, release visibility issues, recent significant changes, and no obvious concerns.

Arguments:

as_of_date
podling: optional podling name filter

`report_narrative_signals`

Return report-derived signals from cached Incubator reports, including latest reported issues, recurring issues across report history, possible copy-forward narrative text between consecutive reports, low observed mentor sign-off, and mismatches between report narrative release claims and health-based release visibility.

When podling is provided, this lookup can use non-current or report-cache-only podlings if matching source data is available.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results
include_signals: optional report narrative signal filter list

`cross_source_mismatches`

Return concrete mismatches between cached report narrative and current health or release evidence, such as a quiet latest report despite elevated health risk, a reported last release with no 12-month release visibility, or a one-report mentor sign-off drop that differs from the rolling average.

When podling is provided, this lookup can use non-current or report-cache-only podlings if matching source data is available.

Arguments:

as_of_date
podling: optional podling name filter
limit: optional max number of results
include_signals: optional cross-source mismatch filter list

`stalled_podlings`

Return podlings matching the strict stalled definition: low commits, low committers, low discussion, and no 12-month releases. This is a narrow subset signal, not a replacement for the watchlist.

Arguments:

as_of_date
limit: optional max number of results

`ipmc_watchlist`

Return podlings that most need IPMC attention based on combined lifecycle and health signals.

Arguments:

as_of_date: optional YYYY-MM-DD date for duration-sensitive views
limit: optional max number of results
severity_at_least: optional minimum severity filter
include_reasons: optional reason filter list

`graduation_readiness`

Assess whether a podling appears ready, near ready, or not yet ready for graduation, with what the sources show against each item of the graduation guide. assessment is one of:

ready: three or more dimensions strong (four in strict_mode), none weak, and every guide item the sources can settle is met. The items in graduation_guide marked needs_person still need a person;
near_ready: close, with the gaps listed in the summary, or ready held back by a guide item not met or not settled, or by a stale source;
not_yet_ready: a graduation requirement is shown not to be met (no IPMC-approved release in 12 months, nobody added since the start, the name search not resolved, or a retirement discussion), or the dimensions are not strong enough;
at_risk: three or more dimensions are weak;
insufficient_data or not_applicable.

The summary of a verdict below ready lists every reason found.

Arguments:

podling: required podling name
as_of_date
include_evidence: optional boolean, defaults to true
strict_mode: optional boolean

A podling that has graduated or retired returns assessment: not_applicable unless as_of_date is before its end date.

release_maturity needs a release within 12 months of as_of_date (or today). The health 12m window is measured from when the health report was generated, so when the podling's latest stated last_release is older than 12 months, the health window only counts if the health data is under a month old. Older health data is flagged in missing_evidence.

General-list mail about the podling is searched live and read for release and governance facts, returned as mail_signals. Each podling gets two searches: its name (newest 20 messages) and its name with "result" (newest 50), so busy vote threads cannot push older release results out of view.

an IPMC release vote [RESULT] on general@ in the last 12 months makes release_maturity strong even when the health window shows no release, and its absence holds it at mixed;
a cancelled vote after the last result lowers release_maturity one step and is listed in blockers, unless a later round of the vote is still open;
a release [VOTE] with no matching [RESULT] or [CANCEL] and mail in the last 21 days is listed in open_release_votes and in missing_evidence;
a retirement discussion in the last 12 months makes governance_health weak and holds the verdict at not_yet_ready;
a "status of" thread in the last 12 months, which is how the IPMC usually opens a retirement question, is listed in status_threads_12m and in missing_evidence.

Only subjects that name a release (the word "release", a version or an RC number) count as release results or cancels, so a [RESULT] on an acceptance or graduation vote is not a release. Results and cancels are matched to their vote ignoring "Apache", "release", "vote" and outcome words such as "PASSED".

Graduation needs positive evidence that the podling has added a committer or PPMC member since it started: a date in any cached report's answer to "When were the last committers or PPMC members elected?", a new committer or PPMC member in the News section of the podling's Incubator status page, or an announcement on dev@. An answer that reports an addition without a date also counts. Without any of these the verdict is at most not_yet_ready, whatever the podling's age, as it is with no release. When a podling more than six months into incubation says in its latest report that nobody has been added, community_independence is weak; when the latest addition found is more than 12 months old it is lowered one step.

For a single podling, its own dev@ list is also read live through MailMCP for the 12 months before as_of_date (or today), and returned as dev_mail_signals, with where it came from in dev_mail_source. Overview tools do not read dev@: a year of one list takes a few seconds. Only subjects, senders and dates are read:

a retirement discussion on dev@ is treated like one on general@: weak governance_health and a verdict held at not_yet_ready;
no dev@ mail for more than 90 days is listed in blockers;
a PPMC release [VOTE] on dev@ with no result in the last 21 days is listed in missing_evidence until the IPMC vote opens on general@;
an announcement of a new committer or PPMC member counts as someone added, and a graduation discussion is noted in the summary.

If dev@ cannot be read, the reason is listed in missing_evidence.

The same single-podling calls also read, live:

the podling's status page at https://incubator.apache.org/projects/<slug>.html, for its News entries (status_page_source);
the PODLINGNAMESEARCH issues in the ASF Jira that name the podling (name_search_source).

graduation_guide lists each guide item with a status and the evidence behind it:

met or not_met: the sources settle it;
unknown: the source could not be read or has no data; this is listed in missing_evidence, never treated as a pass;
needs_person: only a person can judge it, with whatever the sources show as context.

Guide item	How it is shown
Suitable names (the naming process is mandatory)	A PODLINGNAMESEARCH issue resolved as fixed; `not_met` holds the verdict at `not_yet_ready`
Ability to create Apache releases	An IPMC-approved release in the last 12 months
Removing links to old releases from the website	`needs_person`; `release_artifact_evidence` shows the download page links
Recruits committers and PMC members	Someone added since the start (see above)
Recruits users and developers	`needs_person`, with new contributors and dev@ posters from the health report
Not highly dependent on any single contributor	The health report's bus factor proxy: one contributor making half the commits is `not_met`
Three legally independent committers, no single company vital	`needs_person`; no source records affiliations
Collective action, public disagreement, open and inclusive lists	`needs_person`, with dev@ volume and senders
Mentors and IPMC have no remaining issues	`needs_person`, with the latest report's answer on issues for the IPMC and mentor sign-offs
Destination, charter and resolution	`needs_person`
Community graduation vote (recommended, not required)	Graduation threads on dev@ or general@

The status file's tasks are not listed: they are setup tasks every podling does early, and the file is often out of date.

A weak release_maturity also holds the verdict at not_yet_ready, however strong the other dimensions are: graduation requires releases.

source_freshness gives the age in days of the health report and the mail. A source more than 14 days old is listed in stale_sources and missing_evidence, keeps confidence at medium, and holds a ready verdict at near_ready until the source is refreshed. Mail fetched live in the call is 0 days old; mail served only from the cache is as old as its newest copy.

`podling_brief`

Return an IPMC-oriented briefing for one podling.

Arguments:

podling: required podling name
as_of_date
focus: optional area list
brief_format: optional summary or detailed

recent_trajectory reports direction within the preferred health window, while outlook reports readiness levels. These can legitimately disagree, so trajectory_readiness_note carries an explanation when they do and is null when they agree.

sources_used lists only sources that were actually available for the call, so a skipped or missing source is absent rather than appearing as a placeholder location. Availability and the reason for it remain in the explainability block.

`mentoring_attention_needed`

Return podlings where mentoring intervention appears necessary.

Arguments:

as_of_date
limit: optional max number of results
urgency_at_least: optional minimum urgency filter
include_causes: optional cause filter list

`community_health_summary`

Return an IPMC-level summary of community-health patterns across podlings.

Arguments:

as_of_date
scope: optional all_podlings, active_podlings, or reporting_podlings
group_by: optional none, risk_band, mentor_load, or age_band
include_examples: optional boolean

`trademark_naming_check`

Run TrademarkMCP automated naming checks for a proposed Apache project or podling name (reserved marks, Native American check, name format, ASF project-list conflicts, optional GitHub/PyPI/npm lookups).

Arguments:

proposed_name (required)
technical_description: optional, used in the PODLINGNAMESEARCH JIRA template
include_external_search: optional boolean; defaults to false (offline checks only)
asf_min_similarity: optional number 0.0–1.0; defaults to 0.5
trademark_cache: optional TrademarkMCP cache directory

`trademark_branding_check`

Fetch a podling's project website and run TrademarkMCP's Project Branding Requirements checks. Pass podling to look up the website URL from podlings.xml automatically, or pass url explicitly. Defaults to the podling branding stage.

Arguments:

podling: optional; when provided the website URL is resolved from podlings.xml
url: optional; required if podling is omitted
project_name: optional; inferred from the page host if omitted
stage: optional podling, graduation, or tlp; defaults to podling
trademark_cache: optional TrademarkMCP cache directory

`trademark_third_party_check`

Fetch a third-party page and run TrademarkMCP's ASF Trademark Policy checks (domain misuse, branding form, non-affiliation disclaimer, logo misuse, credit link).

Arguments:

url (required)
mark: optional Apache mark (e.g. Kafka, Spark); inferred when omitted
trademark_cache: optional TrademarkMCP cache directory

`refresh_trademark_cache`

Force a fresh fetch of the ASF committees+podlings list used by TrademarkMCP.

Arguments:

trademark_cache: optional TrademarkMCP cache directory

Defaults

When omitted, podlings_source uses --podlings-source, IPMC_PODLINGS_SOURCE, or the ASF podlings.xml URL.
When omitted, health_source uses --health-source, IPMC_HEALTH_SOURCE, or reports if no startup default is set.
When omitted, report_source uses --report-source, IPMC_REPORT_SOURCE, or .cache/incubator-reports if no startup default is set.
When omitted, mail_source uses --mail-source, IPMC_MAIL_SOURCE, or .cache/incubator-general-mail if no startup default is set. If the default cache is missing, IPMC tools use live MailMCP search as a read-only fallback.
When omitted, mail_api_base uses --mail-api-base, IPMC_MAIL_API_BASE, or the public lists.apache.org API.
When omitted, release_dist_base uses --release-dist-base or IPMC_RELEASE_DIST_BASE; if neither is set, ReleaseMCP discovers the podling download page instead of forcing the public Incubator dist release URL.
When omitted, release_archive_base uses --release-archive-base, IPMC_RELEASE_ARCHIVE_BASE, or the public Incubator archive URL.
When omitted, trademark_cache uses --trademark-cache, IPMC_TRADEMARK_CACHE, or TrademarkMCP's default ~/.cache/apache-trademark-mcp.
Oversight views focus on current podlings by default.
Single-podling lookups can still return non-current or report-cache-only podlings when matching source data is available.
Health analysis prefers the freshest available window in this order: 3m, 6m, 12m, to-date.
Source metadata consistently exposes a source field. Health and ReportMCP metadata also preserve the upstream reports_dir field, and MailMCP metadata preserves cache_dir, for compatibility with their source MCPs.

Opinion Model

This server keeps source facts separate from derived opinions. Risk and readiness views are derived from:

mentor coverage
reporting reliability
mentor sign-off signals
community activity
release visibility
incubation duration
participation breadth

The resulting outputs are intended to support IPMC judgment, not replace it.

Opinionated outputs include an explainability object so IPMC members can challenge the result:

source_data_used: the podlings, apache-health, ReportMCP, and MailMCP fields that informed the opinion
reasoning: human-readable explanation of why the opinion was reached
confidence: high, medium, or low. Metric coverage sets the base level (how many of commits, unique committers, report count, mentor sign-offs and dev posters are populated); it is capped at medium while the cached Incubator reports or cached general-list mail for the podling are missing, and missing says which
missing: source evidence that is absent or would improve the assessment

Per-podling tools attach this to podling-level judgments and supporting signals. The community-health summary attaches it to the overall summary and each derived risk theme.

IncubatorMCP is an independent tool and is not a project of the Apache Software Foundation. Apache and related marks are trademarks of The Apache Software Foundation.

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
docs		docs
ipmc		ipmc
tests		tests
.gitignore		.gitignore
AGENTS.md		AGENTS.md
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
ipmc.skill		ipmc.skill
pyproject.toml		pyproject.toml
server.py		server.py

Latest commit

History

Folders and files

Repository files navigation

IPMC MCP

Requirements

Install

Run

Example MCP client config

Test

Coverage

Architecture

Usage Examples

Monthly IPMC Review Workflow

Mentor Checking Their Podlings

General List Mail Evidence

Generating a Board Summary

Tools

configure_sources

current_podlings_overview

recent_changes

significant_changes

reporting_gaps

reporting_reliability

reporting_schedule

release_visibility

release_vote_evidence

release_artifact_evidence

refresh_report_cache

refresh_mail_cache

reporting_cohort

report_narrative_signals

cross_source_mismatches

stalled_podlings

ipmc_watchlist

graduation_readiness

podling_brief

mentoring_attention_needed

community_health_summary

trademark_naming_check

trademark_branding_check

trademark_third_party_check

refresh_trademark_cache

Defaults

Opinion Model

About

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

`configure_sources`

`current_podlings_overview`

`recent_changes`

`significant_changes`

`reporting_gaps`

`reporting_reliability`

`reporting_schedule`

`release_visibility`

`release_vote_evidence`

`release_artifact_evidence`

`refresh_report_cache`

`refresh_mail_cache`

`reporting_cohort`

`report_narrative_signals`

`cross_source_mismatches`

`stalled_podlings`

`ipmc_watchlist`

`graduation_readiness`

`podling_brief`

`mentoring_attention_needed`

`community_health_summary`

`trademark_naming_check`

`trademark_branding_check`

`trademark_third_party_check`

`refresh_trademark_cache`