Uplo Agriculture

AI-powered agricultural knowledge management. Search crop management records, livestock data, compliance documentation, and sustainability reports with struc...

Security Scan

The skill largely matches an agriculture knowledge connector, but there are clear inconsistencies about installation and required credentials and it instructs runtime calls that will send conversation data to an external UPLO instance—verify the package/source and credentials before installing.

Purpose & Capability

The declared purpose (connect to UPLO to search agricultural knowledge) matches the behavior in SKILL.md and README. However, the registry metadata lists no required credentials or env vars while skill.json defines two required config fields (agentdocs_url and api_key) that are necessary to connect to an external UPLO MCP server. That mismatch is incoherent: a connector like this legitimately needs an API endpoint and token, but the registry presentation omitted them.

Instruction Scope

SKILL.md limits runtime actions to mcporter calls (search_knowledge, search_with_context, export_org_context, log_conversation). Those are consistent with a knowledge-base connector. However, SKILL.md does not document the required API credentials or explicitly warn that log_conversation will transmit conversation summaries to the configured UPLO instance. This means user data (conversation summaries, topics, tools_used) will be sent to an external service—expected for this connector but worth explicit notice.

Install Mechanism

The registry lists no install spec (instruction-only), but skill.json contains an mcp stanza that runs 'npx -y @agentdocs1/mcp-server --http' with envs derived from the skill config. That implies the platform will fetch/execute an npm package at runtime. Fetching and executing code via npx from npm is a moderate-risk install path and should be validated (package origin, maintainer, version). The README similarly suggests configuring an MCP server via npx, so the effective install is not purely 'instruction-only'.

Credentials

The skill.json requires agentdocs_url and api_key (a secret) which are proportionate for a connector to an external UPLO instance. The problem is the registry-level requirements list none, and SKILL.md doesn't call out how to supply those creds. Users should be aware the skill needs a token that grants access to their organization's UPLO data; that token will be used by the MCP server process and will be transmitted to/run by the agent runtime.

Persistence & Privilege

always is false and the skill does not request system-level persistence. The skill can be invoked autonomously by the agent (platform default), which is normal. Note: because the skill runs an external MCP server process (via npx) and uses an external API_KEY, autonomous invocation combined with those external credentials increases the impact of any misuse—so validate the MCP package and restrict the API key scope.

What to consider before installing

This skill appears to be a UPLO connector (searching your organization's agriculture knowledge) and that purpose explains the need for an endpoint URL and API key. However, the registry metadata omitted those requirements while skill.json requires them and the README/SKILL.md expect an MCP server launched via npx. Before installing or enabling this skill: 1) Confirm the agentdocs_url is a trusted UPLO endpoint and limit the API key scope/permissions. 2) Inspect or verify the npm package '@agentdocs1/mcp-server' (publisher, versions, audit) since the platform will run it via npx. 3) Understand that 'log_conversation' will send conversation summaries to the UPLO instance—decide what data may be logged and ensure classification/consent. 4) Prefer running the MCP server in an isolated environment or test tenant first. If possible, ask the skill author to (a) update registry metadata to list required config/env vars, (b) document exactly what is transmitted during log_conversation, and (c) pin the MCP package to a specific trusted version.

UPLO Agriculture — Crop & Compliance Intelligence

You have access to organizational knowledge through UPLO, focused on agriculture domain expertise.

Session Start

When you begin a new session, fetch your organizational context:

mcporter call uplo-agriculture.get_identity_context

When to Use

• Questions about agriculture policies, procedures, or processes
• Looking up domain-specific knowledge and documentation
• Finding subject matter experts
• Verifying facts against the knowledge base

Key Tools

Search knowledge:

mcporter call uplo-agriculture.search_knowledge query="your question here"

Search with full context (GraphRAG):

mcporter call uplo-agriculture.search_with_context query="complex question with org context"

Export org context:

mcporter call uplo-agriculture.export_org_context

Get directives:

mcporter call uplo-agriculture.get_directives

Session End

Log the conversation:

mcporter call uplo-agriculture.log_conversation summary="Brief summary" topics='["topic1"]' tools_used='["search_knowledge"]'

Important

• Always cite sources when sharing UPLO information
• Respect classification levels
• If UPLO doesn't have the answer, say so rather than guessing