{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0","slug":"ema-security-agent-identity-verifier-v3-1-0","name":"EMA Agent Identity Verifier v3.1.0","type":"mcp","url":"https://smithery.ai/servers/ema-security/agent-identity-verifier-v3-1-0","page_url":"https://unfragile.ai/ema-security-agent-identity-verifier-v3-1-0","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:ema-security/agent-identity-verifier-v3-1-0"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0__cap_0","uri":"capability://tool.use.integration.wallet.verification.for.ai.agents","name":"wallet verification for ai agents","description":"This capability verifies the authenticity of AI agent wallets by cross-referencing them against a decentralized ledger and a shared database of known bad actors. It employs a consensus mechanism to ensure that wallet statuses are updated in real-time, leveraging the EMA shared brain architecture to instantly flag and block malicious wallets network-wide. This ensures that only trusted agents can initiate transactions, enhancing security across the platform.","intents":["How can I verify the authenticity of an AI agent's wallet before processing a transaction?","What steps do I need to take to ensure that the wallet I'm interacting with is not compromised?","Can I get real-time updates on the status of an AI agent's wallet?"],"best_for":["developers building secure AI applications requiring wallet verification"],"limitations":["Dependent on the availability of the EMA shared brain for real-time updates; if the network is down, verification may be delayed."],"requires":["Access to the EMA shared brain API with valid credentials"],"input_types":["wallet address"],"output_types":["status (TRUSTED/UNVERIFIED/SUSPICIOUS/BLOCK) with signal breakdown"],"categories":["tool-use-integration","security"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0__cap_1","uri":"capability://tool.use.integration.domain.verification.for.ai.agents","name":"domain verification for ai agents","description":"This capability checks the legitimacy of domains associated with AI agents by querying a comprehensive database of registered domains and their reputations. It employs a multi-layered validation process that includes DNS lookups and historical data analysis to assess the trustworthiness of a domain before any transactions occur. This proactive approach helps prevent interactions with potentially harmful agents.","intents":["How can I verify if an AI agent's domain is legitimate before engaging?","What tools do I have to check the reputation of a domain linked to an AI agent?","Can I receive alerts if a domain associated with an agent becomes suspicious?"],"best_for":["developers ensuring the safety of transactions involving AI agents"],"limitations":["Domain verification may be delayed if DNS queries are slow or if the domain is newly registered."],"requires":["Access to the EMA domain verification API"],"input_types":["domain name"],"output_types":["status (TRUSTED/UNVERIFIED/SUSPICIOUS/BLOCK) with signal breakdown"],"categories":["tool-use-integration","security"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0__cap_2","uri":"capability://tool.use.integration.manifest.verification.for.ai.agents","name":"manifest verification for ai agents","description":"This capability validates the manifests of AI agents by parsing and analyzing their structure and contents against predefined schemas and security standards. It ensures that all required fields are present and correctly formatted, while also checking for any suspicious elements that could indicate malicious intent. This verification process is crucial for maintaining the integrity of transactions involving AI agents.","intents":["How can I ensure that an AI agent's manifest is correctly structured and safe to use?","What checks are performed on the manifest of an AI agent before I proceed with a transaction?","Can I validate the manifest of an agent programmatically before executing any actions?"],"best_for":["developers implementing AI agents that require strict manifest validation"],"limitations":["Manifest validation is limited to specific schema formats; unsupported schemas will not be validated."],"requires":["Access to the EMA manifest validation API"],"input_types":["manifest file (JSON, XML)"],"output_types":["status (TRUSTED/UNVERIFIED/SUSPICIOUS/BLOCK) with signal breakdown"],"categories":["tool-use-integration","security"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0__cap_3","uri":"capability://data.processing.analysis.real.time.bad.actor.flagging","name":"real-time bad actor flagging","description":"This capability provides real-time flagging of bad actors by continuously monitoring transactions and interactions across the network. It utilizes a machine learning model trained on historical data to identify patterns associated with malicious behavior, allowing for immediate action to block suspicious agents. This proactive monitoring ensures a safer environment for all transactions.","intents":["How can I get real-time updates on suspicious activities involving AI agents?","What mechanisms are in place to block bad actors instantly across the network?","Can I access historical data on flagged agents for analysis?"],"best_for":["security teams monitoring AI agent interactions"],"limitations":["Real-time monitoring may introduce latency during peak transaction times due to increased data processing."],"requires":["Access to the EMA monitoring API"],"input_types":["transaction data"],"output_types":["alert notifications, flagged agent details"],"categories":["data-processing-analysis","security"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ema-security-agent-identity-verifier-v3-1-0__cap_4","uri":"capability://data.processing.analysis.comprehensive.signal.breakdown.reporting","name":"comprehensive signal breakdown reporting","description":"This capability generates detailed reports on the verification status of AI agents, including a comprehensive signal breakdown that explains the rationale behind each status. It aggregates data from multiple sources, providing insights into the factors contributing to an agent's trustworthiness. This transparency helps users make informed decisions regarding their interactions with AI agents.","intents":["How can I access detailed reports on the verification status of an AI agent?","What factors are considered in determining the trustworthiness of an agent?","Can I obtain a summary report of all flagged agents for review?"],"best_for":["auditors and compliance teams reviewing AI agent interactions"],"limitations":["Reporting features may be limited to a specific number of requests per hour."],"requires":["Access to the EMA reporting API"],"input_types":["agent identifiers"],"output_types":["detailed report (structured data)"],"categories":["data-processing-analysis","security"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["Access to the EMA shared brain API with valid credentials","Access to the EMA domain verification API","Access to the EMA manifest validation API","Access to the EMA monitoring API","Access to the EMA reporting API"],"failure_modes":["Dependent on the availability of the EMA shared brain for real-time updates; if the network is down, verification may be delayed.","Domain verification may be delayed if DNS queries are slow or if the domain is newly registered.","Manifest validation is limited to specific schema formats; unsupported schemas will not be validated.","Real-time monitoring may introduce latency during peak transaction times due to increased data processing.","Reporting features may be limited to a specific number of requests per hour.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.35,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:26.346Z","last_scraped_at":"2026-05-03T15:19:24.053Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=ema-security-agent-identity-verifier-v3-1-0","compare_url":"https://unfragile.ai/compare?artifact=ema-security-agent-identity-verifier-v3-1-0"}},"signature":"kk/II/DdeB20O8pCEwfdGdC/KbqNAPQxdsiak6WHRt4xChEEd+/yWc1rMkkJBIzAYNEkgX3giE/CYitOCzkUCA==","signedAt":"2026-06-20T08:35:50.927Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/ema-security-agent-identity-verifier-v3-1-0","artifact":"https://unfragile.ai/ema-security-agent-identity-verifier-v3-1-0","verify":"https://unfragile.ai/api/v1/verify?slug=ema-security-agent-identity-verifier-v3-1-0","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}