{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_dusk-network-pituitary","slug":"dusk-network-pituitary","name":"pituitary","type":"repo","url":"https://github.com/dusk-network/pituitary","page_url":"https://unfragile.ai/dusk-network-pituitary","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:dusk-network/pituitary"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_dusk-network-pituitary__cap_0","uri":"capability://data.processing.analysis.structural.specification.indexing","name":"structural specification indexing","description":"Pituitary indexes specifications, documentation, and decision records by analyzing the entire corpus structurally rather than relying on a limited context window. This is achieved through a custom-built indexing engine that parses and organizes documents, allowing for comprehensive querying and retrieval based on the full content structure. The use of deterministic algorithms ensures consistent results across different queries.","intents":["How can I quickly find specific specifications across multiple documents?","I need to ensure all my decision records are easily accessible and indexed.","Can I retrieve structured information from my documentation efficiently?"],"best_for":["AI-native teams managing extensive documentation and specifications"],"limitations":["Limited to the scope of indexed documents; unindexed documents cannot be queried."],"requires":["Go 1.16+"],"input_types":["text","structured documents"],"output_types":["structured data","text"],"categories":["data-processing-analysis","documentation-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_dusk-network-pituitary__cap_1","uri":"capability://planning.reasoning.deterministic.drift.detection","name":"deterministic drift detection","description":"This capability monitors specifications and documentation for any changes or 'drifts' from the original intent, using a deterministic algorithm to compare current documents against baseline versions. It flags discrepancies and provides insights into how and when changes occurred, ensuring that teams can maintain alignment with their original goals.","intents":["How can I track changes in my specifications over time?","I want to ensure that my documentation remains aligned with project goals.","Can I receive alerts when my documents deviate from established standards?"],"best_for":["teams needing rigorous compliance and governance over project specifications"],"limitations":["Requires baseline documents to be established for effective drift detection."],"requires":["Go 1.16+"],"input_types":["text","structured documents"],"output_types":["alerts","structured data"],"categories":["planning-reasoning","compliance-monitoring"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_dusk-network-pituitary__cap_2","uri":"capability://safety.moderation.compliance.checking","name":"compliance checking","description":"Pituitary checks documents against predefined compliance criteria using a rule-based engine that evaluates the content against a set of governance policies. This capability allows teams to ensure that all specifications and documentation adhere to organizational standards, providing a clear audit trail of compliance checks.","intents":["How can I verify that my specifications meet compliance requirements?","I need to ensure that all documentation adheres to our governance policies.","Can I automate compliance checks for my project documentation?"],"best_for":["compliance officers and project managers ensuring adherence to standards"],"limitations":["Dependent on the completeness of the compliance criteria defined in the system."],"requires":["Go 1.16+"],"input_types":["text","structured documents"],"output_types":["compliance reports","alerts"],"categories":["safety-moderation","governance"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_dusk-network-pituitary__cap_3","uri":"capability://planning.reasoning.impact.analysis.for.changes","name":"impact analysis for changes","description":"This capability analyzes the potential impact of changes made to specifications or documents by tracing dependencies and relationships within the indexed content. It provides teams with insights into how modifications may affect other parts of the project, facilitating informed decision-making.","intents":["How can I assess the impact of a proposed change to my specifications?","I need to understand how changes in one document affect others.","Can I visualize the dependencies between different specifications?"],"best_for":["project managers and developers assessing change implications"],"limitations":["Requires a well-defined structure in the documentation for accurate impact analysis."],"requires":["Go 1.16+"],"input_types":["text","structured documents"],"output_types":["impact reports","visualizations"],"categories":["planning-reasoning","change-management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_dusk-network-pituitary__cap_4","uri":"capability://safety.moderation.terminology.compliance.checking","name":"terminology compliance checking","description":"Pituitary enforces terminology policies by checking documents against a defined lexicon, ensuring consistent use of terms across specifications and documentation. This is achieved through a built-in terminology engine that flags inconsistencies and suggests corrections, promoting clarity and uniformity in communication.","intents":["How can I ensure consistent terminology in my project documentation?","I want to check if my specifications adhere to defined terminology policies.","Can I automate the enforcement of terminology standards?"],"best_for":["teams focused on maintaining clear and consistent communication"],"limitations":["Effectiveness depends on the completeness of the defined terminology lexicon."],"requires":["Go 1.16+"],"input_types":["text","structured documents"],"output_types":["alerts","suggestions"],"categories":["safety-moderation","communication"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"low","permissions":["Go 1.16+"],"failure_modes":["Limited to the scope of indexed documents; unindexed documents cannot be queried.","Requires baseline documents to be established for effective drift detection.","Dependent on the completeness of the compliance criteria defined in the system.","Requires a well-defined structure in the documentation for accurate impact analysis.","Effectiveness depends on the completeness of the defined terminology lexicon.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.45,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.6,"weights":{"adoption":0.3,"quality":0.2,"ecosystem":0.15,"match_graph":0.3,"freshness":0.05}},"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:20.348Z","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=dusk-network-pituitary","compare_url":"https://unfragile.ai/compare?artifact=dusk-network-pituitary"}},"signature":"bNpcd7jBnJL13lVpdDsq2Pva0pk5KEOVry9+Witjb8IcqRfbokcPr3cE8uNG/vIBHbovgF2bWmDgFW2j/PzTCQ==","signedAt":"2026-06-22T09:23:47.268Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/dusk-network-pituitary","artifact":"https://unfragile.ai/dusk-network-pituitary","verify":"https://unfragile.ai/api/v1/verify?slug=dusk-network-pituitary","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"}}