Question: contribution path for an optional read-only research MCP example

[Michael-aisa-one]

Hi maintainers,

I’m Michael from AIsa. We are exploring a small, optional MCP example for source-backed public SDK or dependency research before implementation.

The scope would be deliberately limited:

• read-only public research only;
• user-provided AISA_API_KEY only, with no credential access beyond that configuration;
• sources, limitations, and possible cost notes shown in the output;
• no change to Klaatu API contracts, default behavior, or coding workflow.

Before building or opening a PR, could you advise whether this fits the preferred path for MCP, hook, skill, or plugin-ecosystem contributions? If it is not a fit, we will keep it as an external community example.

Best,
Michael
AIsa