io.github.agntcy/dir-mcp

Pulls an OASF agent record from the local Directory node by its CID (Content Identifier). The pulled record is content-addressable and can be validated against its hash. Server configuration is set via environment variables (DIRECTORY_CLIENT_SERVER_ADDRESS). Use this tool to retrieve agent records by their CID for inspection or validation.

Pushes an OASF agent record to a Directory server. This tool validates and uploads the record to the configured Directory server, returning: - Content Identifier (CID) for the pushed record - Server address where the record was stored The record must be a valid OASF agent record. Server configuration is set via environment variables (DIRECTORY_CLIENT_SERVER_ADDRESS). Use this tool after validating your record to store it in the Directory.

Searches for agent records on the local directory node using structured query filters. This tool supports flexible wildcard patterns for matching records based on: - Agent names (e.g., "gpt*", "agent-?", "web-*") - Versions (e.g., "v1.*", "*-beta", "v?.0.?") - Skill IDs (exact match only, e.g., "10201") - Skill names (e.g., "*python*", "Image*") - Locators (e.g., "docker-image:*", "http*") - Modules (e.g., "*-plugin", "core*") Multiple filters are combined with OR logic (matches any filter). Results are streamed and paginated for efficient handling of large result sets. Server configuration is set via environment variables (DIRECTORY_CLIENT_SERVER_ADDRESS). Use this tool for direct, structured searches when you know the exact filters to apply.

Verifies that a record's name is owned by the domain it claims. This tool checks that the record was signed with a key published in the domain's well-known JWKS file (/.well-known/jwks.json). You can verify by: - CID: Directly verify a specific record by its Content Identifier - Name: Verify a record by its human-readable name (e.g., "example.com/my-agent") - Name + Version: Verify a specific version (e.g., "example.com/my-agent" + "v1.0.0") Returns verification status and domain verification details including: - The verified domain - The verification method used - The matched key ID from the domain's JWKS Use this tool to verify that an agent record was actually published by the domain owner.

Verifies the digital signature of a record in the Directory by its CID. This tool performs a server-side verification of the record's integrity and authenticity. Returns the verification status (trusted/not trusted). Use this tool to ensure a record has been properly signed and hasn't been tampered with.

Exports an OASF agent record to a different format using the OASF SDK translator. This tool takes an OASF record in JSON format and converts it to the specified target format. Currently supported target formats: - "a2a": Agent-to-Agent (A2A) format - "ghcopilot": GitHub Copilot MCP configuration format - "agentskills": Agent Skills SKILL.md markdown format **Input Format**: Provide the OASF record as a standard JSON object (no wrapper needed). **Output Format**: The output structure depends on the target format: - For "a2a": Returns the A2A card directly as a JSON object - For "ghcopilot": Returns the GitHub Copilot MCP configuration as a JSON object - For "agentskills": Returns a SKILL.md markdown document as plain text Use this tool when you need to convert OASF records to other format specifications.

Retrieves the complete OASF schema JSON content for the specified version. This tool provides direct access to the full schema definition including: - All domain definitions and their IDs - All skill definitions and their IDs - Complete validation rules and constraints - Schema structure and required fields Use this tool to get the complete schema for reference when creating or validating agent records.

Retrieves domains from the OASF schema for the specified version. This tool supports hierarchical domain navigation: - Without parent_domain: Returns all top-level domain categories (e.g., "artificial_intelligence", "software_development") - With parent_domain: Returns sub-domains under that parent (e.g., parent="artificial_intelligence" returns its children) Each domain includes: - name: The domain identifier used in OASF records - caption: Human-readable display name - id: Numeric domain identifier Use this tool to discover valid domains when creating or enriching agent records. Essential for LLM-based enrichment to ensure domains match the schema taxonomy.

Retrieves skills from the OASF schema for the specified version. This tool supports hierarchical skill navigation: - Without parent_skill: Returns all top-level skill categories (e.g., "analytical_skills", "natural_language_processing") - With parent_skill: Returns sub-skills under that parent (e.g., parent="retrieval_augmented_generation" returns its children) Each skill includes: - name: The skill identifier used in OASF records - caption: Human-readable display name - id: Numeric skill identifier Use this tool to discover valid skills when creating or enriching agent records. Essential for LLM-based enrichment to ensure skills match the schema taxonomy.

Imports data from a different format to an OASF agent record using the OASF SDK translator. This tool takes data in a source format and converts it to OASF record format. Currently supported source formats: - "mcp": Model Context Protocol format - "a2a": Agent-to-Agent (A2A) format - "agentskills": Agent Skills SKILL.md markdown format **CRITICAL - Input Format Requirements**: For "mcp" format, provide source_data as: { "server": { "name": "example-server", "version": "1.0.0", ... (rest of MCP server data) } } For "a2a" format, provide source_data as either: 1) wrapped object: { "a2aCard": { "name": "example-agent", "version": "1.0.0", "description": "...", ... (rest of A2A card data) } } 2) or direct A2A card object. For "agentskills" format, provide source_data as a JSON object with a "skillMarkdown" field: { "skillMarkdown": "---\nname: my-skill\ndescription: ...\n---\n\nBody..." } **Important - Enrichment Required**: The domains and skills in the resulting OASF record from the oasf-sdk translator are incomplete and MUST be enriched. Follow these steps: 1. Remove any existing domains and skills fields from the imported record 2. Use agntcy_oasf_get_schema_domains to discover valid domain options: - First get top-level domains (without parent_domain parameter) - Then explore sub-domains using the parent_domain parameter if needed 3. Use agntcy_oasf_get_schema_skills to discover valid skill options: - First get top-level skill categories (without parent_skill parameter) - Then explore sub-skills using the parent_skill parameter if needed 4. Analyze the source content to select the most relevant domains and skills 5. Add the selected domains and skills to the record with proper names and IDs Use this tool when you need to convert records from other format specifications to OASF. For a complete guided workflow including enrichment and validation, use the import_record prompt.

Lists all available OASF schema versions supported by the server. This tool provides a simple way to discover what schema versions are available without having to make requests with specific version numbers. Use this tool to see what OASF schema versions you can work with.

Validates an AGNTCY OASF agent record against the OASF schema. This tool performs comprehensive validation including: - Required fields check - Field type validation - Schema-specific constraints - Domain and skill taxonomy validation Returns detailed validation errors to help fix issues. Use this tool to ensure a record meets all OASF requirements before pushing.