Build MCP Server: NEAR NFT Operations

Description

## Overview
Create an MCP server for NEAR NFT operations - viewing collections, checking ownership, understanding NFT metadata, and interacting with major NFT platforms.

## Why This Matters
NFTs are a major use case on NEAR with platforms like Paras, Mintbase, and Few and Far. Claude should be able to help users explore and understand NFTs.

## Technical Requirements

### MCP Tools
```typescript
// 1. get_nft_collection
// Get collection info and stats
// Input: { contract_id: string }
// Output: { name, total_supply, floor_price, holders, volume }

// 2. get_owned_nfts
// List NFTs owned by an account
// Input: { account_id: string }
// Output: Array of { collection, token_id, name, image, rarity }

// 3. get_nft_metadata
// Full metadata for a specific NFT
// Input: { contract_id, token_id }
// Output: { title, description, media, attributes, owner, history }

// 4. search_nfts
// Search NFTs by name, trait, or collection
// Input: { query: string, collection?: string }
// Output: Array of matching NFTs

// 5. get_nft_activity
// Recent sales, listings, transfers
// Input: { contract_id?: string, account_id?: string }
// Output: Array of activity events

// 6. estimate_mint_cost
// Calculate cost to mint NFT(s) on NEAR vs other chains
// Input: { count: number, metadata_size: "small"|"medium"|"large" }
// Output: { near_cost, eth_cost, sol_cost, savings }
```

### Integrations
- Paras API for Paras NFTs
- Mintbase API for Mintbase NFTs
- NEP-171 standard for any NFT contract
- Price feeds for floor prices

## Deliverables
1. **MCP server** with NFT functionality
2. **Support for major NEAR NFT platforms**
3. **Cost comparison to highlight NEAR's advantages**
4. **Published and documented**

## Budget: 12 NEAR