pulsemcp verified Safe content atomic mcp-remote

Advocu

This MCP server provides activity reporting capabilities for Google Developer Experts (GDEs) through the Advocu platform, enabling AI assistants to submit various types of professional activities including content creation, public speaking, workshops, mentoring sessions, product feedback, Googler interactions, and stories. Built by Carlos Azaustre using TypeScript with the MCP SDK and dotenv for configuration, it features comprehensive activity type support with detailed metrics tracking (readers, attendees, time spent, impact), structured data validation with proper schemas for each activity type, and direct API integration with the Advocu reporting system using Bearer token authentication. The implementation includes extensive enum definitions for tags, content types, event formats, countries, and significance categories, making it valuable for GDEs who need to streamline their activity reporting workflow, developer advocates tracking their community engagement metrics, and any professional needing structured reporting of technical community activities.

Cognium trust score

91%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: data-analytics
Source: PulseMCP
Repository: github.com/carlosazaustre/advocu-mcp-server
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Advocu from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"