Add Maeve Social MCP server

[jared-james]

Adds the hosted Maeve Social Streamable HTTP MCP server to the registry. The entry uses the public maeve-agent repository, documents OAuth and optional API-key authentication, and includes representative tools for workspace discovery, integration capabilities, content drafting and scheduling, publishing, media, and analytics. Validation: PYTHONUTF8=1 python validate.py.

[madeburo]

hi @jared-james
thanks for pr! Hosted endpoint is live, its OAuth protected-resource metadata is available and version 0.7.3 matches the current public release. However, I’m requesting changes for a few correctness and usability issues:

• This is a remote-only MCP, but the registry entry does not contain its actual endpoint (https://api.maevesocial.com/mcp) or any usable connection configuration. The repository URL cannot substitute for the MCP endpoint. Since the current registry schema has no remotes or remote_url field, we should add that support first or hold this entry until remote servers can be represented correctly.

• The linked repository states that it does not contain Maeve’s private application repositories. It provides the agent plugin, configuration, and documentation, but not the hosted MCP implementation. Please clarify whether closed-source hosted servers are accepted by the registry, whose repository field is currently defined as the source-code repository.

• publish_now.confirmationText is documented as mandatory and never auto-confirmable, but it is missing from the tool schema’s required array. Please add it to prevent the registry schema from advertising an unsafe or invalid call.

• get_analytics_summary.days has no JSON Schema type. Please model its actual accepted values, including the documented 1–90 day range or all.

• Maeve’s documentation says tool availability is dynamic and relies on search_mcp_tools, get_active_mcp_tools, and activate_mcp_toolsets. These discovery tools should be included, or the entry should clearly explain that the listed tools may require toolset activation.

The validator passes, but it only verifies the YAML structure and does not catch these operational or tool-schema issues.